You are on page 1of 104

Title page

Alcatel-Lucent
Base Station Subsystem |
Telecom Routing Configuration
3MN-01075-1873-PGZZA
Issue 6 | November 2012

Legal notice
Legal notice

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2012 Alcatel-Lucent. All rights reserved.
Note:

Not to be used or disclosed except in accordance with applicable agreements.

Contents
About this document
Purpose

............................................................................................................................................................................................. xi
xi

Reason for reissue

........................................................................................................................................................................ xi
xi

New in this release

....................................................................................................................................................................... xi
xi

Intended audience

....................................................................................................................................................................... xii
xii

Supported systems

...................................................................................................................................................................... xii
xii

How to use this document


Prerequisites

........................................................................................................................................................ xii
xii

.................................................................................................................................................................................. xii
xii

Conventions used

........................................................................................................................................................................ xii
xii

Related information ................................................................................................................................................................... xiii


xiii
Document support ...................................................................................................................................................................... xiii
xiii
Technical support
How to order

................................................................................................................................................................................ xiii
xiii

How to comment
1

....................................................................................................................................................................... xiii
xiii

........................................................................................................................................................................ xiii
xiii

Introduction
Overview ...................................................................................................................................................................................... 1-1
1-1
Required Hardware Elements ............................................................................................................................................... 1-1
1-1
BSS Architecture ....................................................................................................................................................................... 1-2
1-2
IP Telecom Networks Overview .......................................................................................................................................... 1-7
1-7
BSS Communication Plan ................................................................................................................................................... 1-10
1-10
LAN Configuration and Subnet Summary .................................................................................................................... 1-11
1-11
General Rules for IP Addressing ....................................................................................................................................... 1-13
1-13
IP TimeToLive Values for BSS over IP .......................................................................................................................... 1-13
1-13

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
iii
3MN-01075-1873-PGZZA
Issue 6 November 2012

Contents
....................................................................................................................................................................................................................................

IP Transport Management in 9130 BSC Evolution


Overview ...................................................................................................................................................................................... 2-1
2-1
IP Addressing Rules ................................................................................................................................................................. 2-1
2-1
O&M and Telecom with one shared subnet .................................................................................................................... 2-2
2-2
Several Subnets for Separate O&M and Telecom ...................................................................................................... 2-10
2-10
Reachability Test

.................................................................................................................................................................... 2-22
2-22

IP Transport Management in 9130 MFS Evolution


Overview ...................................................................................................................................................................................... 3-1
3-1
LAN Configuration .................................................................................................................................................................. 3-1
3-1
IP Addressing Rules ................................................................................................................................................................. 3-2
3-2
Several Subnets for Separate O&M and Telecom ......................................................................................................... 3-2
3-2
Reachability Test ..................................................................................................................................................................... 3-11
3-11
O&M Reachability Test

....................................................................................................................................................... 3-12
3-12

Telecom Reachability Test by Control Station

............................................................................................................ 3-14
3-14

Telecom Reachability Test by the GPU .......................................................................................................................... 3-16


3-16
Reachability Test Rules ........................................................................................................................................................ 3-18
3-18
4

IP Transport Management in 9125 TC


Overview ...................................................................................................................................................................................... 4-1
4-1
LAN Configuration .................................................................................................................................................................. 4-1
4-1
Reachability Test ....................................................................................................................................................................... 4-7
4-7

IP Transport Management in 9100 BTS


Overview ...................................................................................................................................................................................... 5-1
5-1
9100 BTS IP Addressing in IP over E1 (IPoE1) Configuration ............................................................................... 5-1
5-1
9100 BTS IP Addressing in IP over Ethernet (IPoEth) Configuration .................................................................. 5-4
5-4
Security Interface Specifications ......................................................................................................................................... 5-7
5-7
BTS NEM users ......................................................................................................................................................................... 5-8
5-8

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
iv
3MN-01075-1873-PGZZA
Issue 6 November 2012

Contents
....................................................................................................................................................................................................................................

Bidirectional Forwarding Detection (BFD) Protocol ................................................................................................ 5-11


5-11
6

BSS Firewall Configuration


Overview ...................................................................................................................................................................................... 6-1
6-1
Port Handling

............................................................................................................................................................................. 6-1
6-1

Firewall Positions and Concerned Flows ......................................................................................................................... 6-3


6-3
7

DHCP Server
Overview ...................................................................................................................................................................................... 7-1
7-1
DHCP Server Located on 9153 OMC-R .......................................................................................................................... 7-1
7-1
DHCP Server Located External to 9153 OMC-R ......................................................................................................... 7-2
7-2
Without a DHCP Server
DHCP Relay

......................................................................................................................................................... 7-3
7-3

............................................................................................................................................................................... 7-3
7-3

STM1 on 9130 BSC Evolution and 9125 TC


Overview ...................................................................................................................................................................................... 8-1
8-1
Introduction ................................................................................................................................................................................. 8-1
8-1

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
v
3MN-01075-1873-PGZZA
Issue 6 November 2012

Contents
....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
vi
3MN-01075-1873-PGZZA
Issue 6 November 2012

List of tables
1-1

O&M / Telecom Flow Segregation Table

...................................................................................................... 1-10

1-2

LAN Configuration and Subnet Summary

.................................................................................................... 1-12

1-3

BSS over IP TimeToLive Values

2-1

Telecom Parameters for Definition of Subnet A

............................................................................................ 2-3

2-2

The telecom parameters for the reachability test

........................................................................................... 2-6

2-3

The external IP addresses for O&M

2-4

The external IP addresses for A Signalling over IP (AsigoIP)

2-5

The external IP addresses for ASig over IP: symmetric Multi-homing

2-6

The external IP addresses for A User Plane over IP (AUPoIP)

2-7

The external IP addresses for BSS over IP (BSSoIP) ................................................................................... 2-9

2-8

The external IP addresses for Lb / Iur-g over IP

2-9

The telecom parameters for the definition of the subnets

2-10

The external IP addresses for O&M

2-11

The external IP addresses for A Signaling over IP (AsigoIP)

2-12

The external IP addresses for ASig over IP: symmetric Multi-homing for AsigoIP

2-13

The external IP addresses for A User Plane over IP (AUPoIP)

2-14

The external IP addresses for BSS over IP (BSSoIP)

2-15

The external IP addresses for Lb / Iur-g over IP .......................................................................................... 2-21

2-16

The 9130 BSC Evolution flow and switch ports

2-17

VLAN Conf Index description ........................................................................................................................... 2-22

3-1

Parameters for LAN Configuration

3-2

MFS Flow and Switch Ports

3-3

Telecom Parameters for Definition of Gb Subnet

....................................................................................................................... 1-13

................................................................................................................... 2-7
.................................................................. 2-8
................................................. 2-8

................................................................ 2-8

............................................................................................ 2-9
........................................................................ 2-14

................................................................................................................. 2-19
................................................................. 2-19
...................... 2-19

.............................................................. 2-20

................................................................................ 2-20

......................................................................................... 2-21

.................................................................................................................... 3-4

.................................................................................................................................. 3-5
......................................................................................... 3-5

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
vii
3MN-01075-1873-PGZZA
Issue 6 November 2012

List of tables
....................................................................................................................................................................................................................................

3-4

Telecom Parameters for Definition of Gb Subnet

......................................................................................... 3-5

3-5

IP-Adressing Inside MFS for Gb-over-IP Table ............................................................................................. 3-6

3-6

Telecom Parameters for Definition of BSS/IPGSL Subnet ........................................................................ 3-8

3-7

IP Assignment Rules in BSS/IPGSL Subnet

3-8

Telecom Parameters for Definition of BSS/IPGCH Subnet

3-9

IP Assignment Rules in BSS/IPGCH Subnet ................................................................................................ 3-10

3-10

O&M Reachability Test Address

3-11

Control Station Telecom Reachability Test Address

3-12

GPU Telecom Reachability Test Address ....................................................................................................... 3-16

4-1

Parameters for LAN Configuration

4-2

TC Flow and Ports

5-1

Parameters for LAN Configuration

5-2

Parameters for Subnet E .......................................................................................................................................... 5-3

5-3

Address Plan for BTS in IP over E1 (IPoE1) Configuration

5-4

Parameters for LAN Configuration

5-5

Parameter for BFD Protocol ................................................................................................................................ 5-11

6-1

Flow Port Ranges

................................................................................................... 3-9
.................................................................... 3-10

....................................................................................................................... 3-12
.................................................................................. 3-14

.................................................................................................................... 4-2

.................................................................................................................................................... 4-4
4-4
.................................................................................................................... 5-2

..................................................................... 5-3

.................................................................................................................... 5-4

...................................................................................................................................................... 6-1
6-1

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
viii
3MN-01075-1873-PGZZA
Issue 6 November 2012

List of figures
1-1

Full IPoEth BSS

......................................................................................................................................................... 1-2
1-2

1-2

Different LAN BSS Architecture ......................................................................................................................... 1-6

1-3

One LAN BSS Architecture ................................................................................................................................... 1-7

1-4

IP Telecom Networks

............................................................................................................................................... 1-8
1-8

1-5

IP Telecom Networks

............................................................................................................................................... 1-9
1-9

2-1

9130 BSC Evolution in one LAN configuration with VRRP (O&M and Telecom are mixed)

2-2

9130 BSC Evolution in one LAN configuration without VRRP (O&M and Telecom are mixed)
................................................................................................................................................................................. 2-32-3
2-3

2-3

9130 BSC Evolution in one LAN configuration with VRRP (O&M, AsigoIP, BSSoIP, Lb / Iur-g
AUPoIP are separated) ....................................................................................................................................... 2-11

2-4

9130 BSC Evolution in one LAN configuration without VRRP (O&M, AsigoIP, BSSoIP, Lb /
Iur-g and AUPoIP are separated) .................................................................................................................... 2-13

3-1

9130 MFS Evolution O&M Reachability Test

3-2

9130 MFS Evolution Telecom Reachability Test by Control Station

3-3

9130 MFS Evolution Telecom reachability Test by GPU

4-1

9125 TC in One LAN Configuration (O&M and Telecom are Mixed)

4-2

Two Subnets for Separate O&M and Telecom

5-1

BTS IP in IP over E1 (IPoE1) Configuration

6-1

Standard Case .............................................................................................................................................................. 6-3


6-3

6-2

BSC in Access Network and Central Office

.................................................................................................... 6-4

6-3

MSC in Access Network and Central Office

................................................................................................... 6-4

8-1

SDH Ring Configuration

8-2

ADM Functional Description ................................................................................................................................ 8-3

.... 2-2

............................................................................................. 3-13
.................................................. 3-15

........................................................................ 3-17
................................................. 4-5

............................................................................................... 4-6

.................................................................................................. 5-2

........................................................................................................................................ 8-2

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
ix
3MN-01075-1873-PGZZA
Issue 6 November 2012

List of figures
....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
x
3MN-01075-1873-PGZZA
Issue 6 November 2012

About this document


About this document

Purpose

This document describes the generic BSS Telecom Routing Configuration applicable for
all hardware in the BSS.
Reason for reissue
Issue number

Reason for reissue

The section O&M and Telecom with one shared


subnet (p. 2-2)was updated.

The following sections were updated:

9100 BTS IP Addressing in IP over Ethernet


(IPoEth) Configuration (p. 5-4)

Supported systems (p. xii)

The following sections were updated:

Telecom Reachability Test by the GPU (p. 3-16)

Reachability Test (p. 3-11)

Added the OS 6850E router.

Due to the introduction of ASig over IP: symmetric


Multi-homing feature, the following section was
modifiedChapter 2, IP Transport Management in 9130
BSC Evolution

First official release of the document.

New in this release

This section contains information about changes to the current document.

...................................................................................................................................................................................................................................
Alcatel-Lucent BSS
xi
3MN-01075-1873-PGZZA
Issue 6 November 2012

About this document


....................................................................................................................................................................................................................................

New features

ASig over IP: symmetric Multi-homing


Other changes

None.
Intended audience

This document is intended for:

Marketing Product and Support personnel

Development Center personnel


Technical Assistance Center personnel
Customer Services personnel

Validation and System Specifications personnel.

Supported systems

This document applies to Release B12 of the BSS.


This document contains IPoE1 related information. This feature is available commercially
from Release LR13.
How to use this document

No specific recommendation applies regarding the way readers should read this
document.
Prerequisites

You must have a basic understanding of Alcatel-Lucent BSS equipment and IP routing
Conventions used

This section gives information on conventions.


Vocabulary conventions

None.
Typographical conventions

The following typographical conventions are used in this document:


Appearance

Description

Italicized text

Emphasized information.

graphical user interface text

Text that is displayed in a graphical user interface or in a


hardware label.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
xii
3MN-01075-1873-PGZZA
Issue 6 November 2012

About this document


....................................................................................................................................................................................................................................

Appearance

Description

Document reference, reference


number

Related document that is referenced in the document.

Related information

None.
Document support

For support in using this or any other Alcatel-Lucent document, contact Alcatel-Lucent at
one of the following telephone numbers:

1-888-582-3688 (for the United States)


1-317-377-8618 (for all other countries)

Technical support

For technical support, contact your local Alcatel-Lucent customer support team. See the
Alcatel-Lucent Support web site (http://www.alcatel-lucent.com/support/) for contact
information.
How to order

To order Alcatel-Lucent documents, contact your local sales representative or use Online
Customer Support (OLCS) (http://support.alcatel-lucent.com)
How to comment

To comment on this document, go to the Online Comment Form (http://infodoc.alcatellucent.com/comments/) or e-mail your comments to the Comments Hotline
(comments@alcatel-lucent.com).

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
xiii
3MN-01075-1873-PGZZA
Issue 6 November 2012

About this document


....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
xiv
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction
1

Overview
Purpose

This Overview gives information needed for smth.


Contents
Required Hardware Elements

1-1

BSS Architecture

1-2

IP Telecom Networks Overview

1-7

BSS Communication Plan

1-10

LAN Configuration and Subnet Summary

1-11

General Rules for IP Addressing

1-13

IP TimeToLive Values for BSS over IP

1-13

Required Hardware Elements


Overview

The Layer 3 Switch must support the following features:

DHCP server for DHCP relay to forward client requests


Network Time Protocol (NTP) for network wide time synchronization
Port based, port mirroring for troubleshooting and lawful interception

Dual image and dual configuration file storage provides backup


Remote telnet management or secure shell access using SSH
Secured file upload using SFTP.

...................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-1
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

Required Hardware Elements

....................................................................................................................................................................................................................................

Required Layer 3 Routing Protocols (IPv4):

Network protocols: TCP/IP stack, ARP, DHCP relay

IP Routing: OSPF v2
Redundancy: VRRP v2.

BSS Architecture
IPoEth BSS Architecture

In this configuration, there is IPoEth on Abis and Ater.


9130 BSC, TC, 9130 MFS are connected through the IP network of the operator.
The CS user plane is passed directly to the TC over IP, while the CS control plane is
directed towards the BSC.
This is show in the following figure.
Figure 1-1 Full IPoEth BSS

IPoE1 BSS Architecture

In this configuration, there is IPoE1 on Abis and IPoEth on Ater.


It is an intermediate step towards a full IPoEth network solution: 9130 BSC, TC, 9130
MFS and 9153 OMC-R are connected through the IP network of the operator.
However, BTS are still connected through E1 links.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-2
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

BSS Architecture

....................................................................................................................................................................................................................................

This mode preserves the existing E1 links on the Abis interface and introduces IP
transport using the Point-to-Point Protocol (PPP) or the Multi Link Point-to-Point
Protocol (ML-PPP) in the case of more than one E1 link.
Those protocols are used to encapsulate the IP traffic within HDLC frames, which are
then sent over the E1 links. In this mode, all traffic is routed towards the BSC.
The following figure shows the BSS with IPoE1 on Abis (and IP backbone on Ater).

( 1): Due to the mixed mode, some E1 links in Atermux are kept until all BTS have
switched to IP mode. This must be taken into account in order to ensure IP to TDM come
back mechanisms inside the TC (in the case of failure of one TC board).
( 2): This link allows to transmit some part (or the totality) of the Gb traffic through a set
of TS of the A interface E1 links. This traffic is cross connected through the MFS, the TC
and the MSC towards the SGSN (note that the MSC-SGSN link is not the Gs interface). It
is called the "Gb insertion" mode and is only possible if CS and PS traffic share the same
Ater-mux E1 link. This mode is not supported in IP transport mode (this would be needed
only for the few BTSs which remain in TDM mode in mixed mode, we assume that the
operator will switch to IP the major part of its BTSs; moreover, the GboIP feature is
available). In this particular case, going to IP mode will require the operator to add a new
E1 link on Gb.
Mixed Mode BSS Architecture

This mode allows the BSS to handle at the same time some BTS in TDM mode (for B10)
and others in IP mode (IPoE1 or IPoEth).

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-3
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

BSS Architecture

....................................................................................................................................................................................................................................

This mode allows the BSS to handle at the same time some BTS in TDM mode (for B10)
and others in IP mode (IPoEth).
It provides the operator with a "step by step" introduction of IP in the network.
Layer 2 BSS Architecture

Using a Layer 2 transport network means that, despite the fact that the BSS NEs (BTS,
BSC, TC, MFS) will still exchange IP packets, the underlying functional architecture of
the transport network can be seen as a single LAN (in practice, an Ethernet LAN). Taking
into account the potential distance between network elements, this will be based on
"Extended Area LAN" concepts such as the MetroEthernet. The primary impact on the
IP-based transport is that all IP addresses of the NEs belong to the same IP subnet.
It has at least one IP router in the BSS transmission network. If needed, this IP router can
be added (anywhere) on top of an Ethernet network, s shown in the example highlighted
in the figure below.

Ethernet switches 1, 2, 3, 4 are access points to the operator's network.


The core Ethernet switch represents the interconnections inside the operator's network.
VLAN tags 1, 2, 3 represent traffic from / to Ethernet LANs 1, 2, 3. They can be
configured on the Ethernet switches 1, 2, 3, 4, the core network nodes, and the router.
Since there are three different VLANs, there are also three different IP subnets, and the
Router must be assigned one IP address in each of these subnets.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-4
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

BSS Architecture

....................................................................................................................................................................................................................................

A fourth subnet can be defined for the central office, with IP addresses for TC, MFS,
BSC, and the IP router (with VLAN 4). VLAN 1 and two are only needed if the operator
wants to (or must) manage different subnets for BTS in LANs 1 and 2 (i.e. a specific IP
address space for the BTSs in each LAN).
If the same subnet is used for all these BTSs, the same VLAN tag can be used for LAN 1
and 2. VLAN 3 is only needed if BSC is not in this subnet, as well as VLAN 4 for the
Central Office controllers.
No route needs to be configured on the IP router, since only its local interfaces are
involved in the used routes
Layer 3 BSS Architecture

The Layer 3 Alcatel-Lucent OmniSwitch 6850/6850E is used as an example for


configuring the BSS layer 3 architecture.
For more information about OmniSwitch 6850/6850E, refer to Alcatel-Lucent Base
Station Subsystem - BSS O&M Routing Configurations (3MN-01075-1871-PGZZA).
Controllers in Different Networks

MFS, BTS, TC are in different sub networks. In this case, each machine defines its proper
subnet, as shown in the following figure.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-5
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

BSS Architecture

....................................................................................................................................................................................................................................

Figure 1-2 Different LAN BSS Architecture

All Controllers in Same Network

MFS, BTS, TC are in the same subnetwork, as shown in the figure below.
Common subnet allows the operator to:

Simplify the IP management (only one subnet to manage)

Save IP ports on the routers (L3 ports on routers are more expensive than L2 ports).

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-6
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

BSS Architecture

....................................................................................................................................................................................................................................

Figure 1-3 One LAN BSS Architecture

IP Telecom Networks Overview


Overview

The IP Telecom Network carries high traffic with a high level of reliability.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-7
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

IP Telecom Networks Overview

....................................................................................................................................................................................................................................

Figure 1-4 IP Telecom Networks

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-8
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

IP Telecom Networks Overview

....................................................................................................................................................................................................................................

Figure 1-5 IP Telecom Networks

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-9
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

BSS Communication Plan

....................................................................................................................................................................................................................................

BSS Communication Plan


Overview

The following table represents the communication plan.


Table 1-1

O&M / Telecom Flow Segregation Table

9130
BSC
Evolution

9130
MFS
Evolution

9135
MFS

9125
TC

9100
BTS

9153
OMC-R

MSC

SGSN

9130 BSC
Evolution

Not
applicable

Telecom

Not
applicable

Telecom

Telecom

O&M

Telecom

Telecom

9130 MFS
Evolution

Telecom

Not
applicable

Not
applicable

Not
applicable

Telecom

O&M

Telecom

Telecom

9135 MFS

Not
applicable

Not
applicable

Not
applicable

Not
applicable

Not
applicable

O&M

Telecom

Telecom

9125 TC

Telecom

Not
applicable

Not
applicable

Telecom

Telecom

O&M

Telecom

Not
applicable

9100 BTS

Telecom

Not
applicable

Not
applicable

Telecom

Telecom

O&M

Not
applicable

Not
applicable

9153 OMC-R

O&M

O&M

O&M

O&M

O&M

O&M

Not
applicable

Not
applicable

TC NEM

Not
applicable

Not
applicable

Not
applicable

O&M

Not
applicable

Not
applicable

Not
applicable

Not
applicable

9130 BSC
Evolution NEM

O&M

Not
applicable

Not
applicable

Not
applicable

Not
applicable

Not
applicable

Not
applicable

Not
applicable

9135 MFS / 9130


MFS Evolution
IMT

Not
applicable

O&M

O&M

Not
applicable

Not
applicable

Not
applicable

Not
applicable

Not
applicable

BTS NEM

Not
applicable

Not
applicable

Not
applicable

Not
applicable

O&M

Not
applicable

Not
applicable

Not
applicable

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-10
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

BSS Communication Plan

....................................................................................................................................................................................................................................

The MFS IMT, BTS NEM, BSC NEM,TC NEM dialogue with corresponding NE in the
O&M communication plan. NEM remotely connected to an NE are usually located in an
O&M site. To have a NEM connected from a telecom site, the O&M addresses must be
routable up to this site.
MSC and SGSN are not BSS NE but core network NEs with interfaces with the BSS.

LAN Configuration and Subnet Summary


Overview

The following table lists the different LAN configurations and related subnets.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-11
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

LAN Configuration and Subnet Summary

....................................................................................................................................................................................................................................

Table 1-2

LAN Configuration and Subnet Summary

LAN Topology

IP Transport
Mode Possibility

External
Subnet(s)

Network
Element
Impacted

Comments

One LAN

O&M only

As follows:

A is the only one


external subnet
dedicated to O&M

O&M and Telecom


with one shared
subnet

O&M and Telecom


with two separate
subnets

Two LAN

A1, A2

O&M and Telecom


with separate
subnets and with
several telecom
subnets

A1, A2, A3, A4, A5

O&M only

9130 MFS
Evolution

9135 MFS

9130 BSC
Evolution

9125 TC

As follows:

9130 MFS
Evolution

9130 BSC
Evolution

9125 TC

As follows:

9130 MFS
Evolution

9135 MFS

9130 BSC
Evolution

9125 TC

As follows:

9130 MFS
Evolution

9130 BSC
Evolution

As follows:

9130 MFS
Evolution

9130 BSC
Evolution

A is the external
Subnet shared by
O&M and Telecom

A2 is the external
subnet with
Telecom when A1
is dedicated to
O&M

A2, A3, A4, A5 are


the external subnets
with Telecom when
A1 is dedicated to
O&M
A is the external
subnet and there are
2 local subnets
named B and C

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-12
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

General Rules for IP Addressing

....................................................................................................................................................................................................................................

General Rules for IP Addressing


Overview

The operator must be able to group the IP addresses according to his own organization.
The operator must be able to use more than one 9130 BSC / MFS Evolution on a single
subnet. This requirement aims at reducing the number of subnets handled by the external
routers, which allows using lower cost routers. This requirement is especially interesting
when several 9130 BSC Evolution are co-localized or when the 9130 BSC Evolution is
co-localized with the 9130 MFS Evolution.
The operator must be able to separate the O&M IP addresses from the Telecom IP
addresses in two different subnets.
The first and the last IP addresses in a subnet are reserved, respectively to identify the
subnet addresses and the broadcast address. They must be removed from the list of IP
addresses that can be assigned to the hosts. For instance, let assume that Subnet_IP_Addr
= 150.100.12.128 and Subnet_Mask = 255.255.255.128. Then, the hosts can be only
assigned in the range 150.100.12.129 to 150.100.12.254.
External router is part of the customer network and it is up to the customer to configure it
with IP addresses.

IP TimeToLive Values for BSS over IP


Overivew

The following table represents the IP TimeToLive values for BSS over IP:
Table 1-3

BSS over IP TimeToLive Values

BTS
IPTCH
MUXTRAUP

BSC

MFS

64

TC

NTP server

16

16

IPTCH
eTRAUP
IPGCH-C

255

64

IPGCH-U

255 for
MC-TRX, or
64 for others

64

OML

64

64

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-13
3MN-01075-1873-PGZZA
Issue 6 November 2012

Introduction

IP TimeToLive Values for BSS over IP

....................................................................................................................................................................................................................................

Table 1-3

RSL

BSS over IP TimeToLive Values

BTS

BSC

255 for
MC-TRX, or
64 for others

64

MFS

(continued)
TC

IPGSL

64

TCSL

64

64

IP_BSSASIG

64

64

SNMP

64

NTP

64

NTP server

64

255

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
1-14
3MN-01075-1873-PGZZA
Issue 6 November 2012

I2P Transport Management


in 9130 BSC Evolution

Overview
Purpose

This section is dedicated to the IP addressing of the 9130 BSC Evolution subsystem only
Contents
IP Addressing Rules

2-1

O&M and Telecom with one shared subnet

2-2

Several Subnets for Separate O&M and Telecom

2-10

Reachability Test

2-22

IP Addressing Rules
Overview

IP addresses for a 9130 BSC Evolution can be chosen freely, limited only by the
following rules:
9130 BSC Evolution external addresses must not belong to the following networks:

172.16/16, 172.17/16, 172.18/16


192.168.<SGA>.65, 192.168.<SGA>.66 where <SGA> means Shelf Geographical
Address and can have the value 3 or 4.

OMC-Rs or other equipment with which the 9130 BSC Evolution interacts must not
belong to the following networks:

172.16/16, 172.17/16, 172.18/16

192.168.<SGA>.65, 192.168.<SGA>.66 where <SGA> means Shelf Geographical


Address and can have the value 3 or 4

...................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-1
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

IP Addressing Rules

....................................................................................................................................................................................................................................

Customer is free to use these network, provided these networks or machines on this
network do not interact with 9130 BSC Evolution
In the case of an O&M link on ML-PPP (O&M link over Ater), 9130 BSC Evolution
external addresses must not belong to the network 1.1.1.0/29.

O&M and Telecom with one shared subnet


Overview

For both O&M transport and Telecom transport, there is used one external subnet, as
shown in the following figure:
Figure 2-1 9130 BSC Evolution in one LAN configuration with VRRP (O&M and
Telecom are mixed)

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-2
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

O&M and Telecom with one shared subnet

....................................................................................................................................................................................................................................

Figure 2-2 9130 BSC Evolution in one LAN configuration without VRRP (O&M and
Telecom are mixed)

The subnet A is the external and visible subnet from the IP O&M / Telecom Network.
There are dedicated IP addresses for the Telecom transport.
For the definition of the subnet A, the necessary telecom parameters are set in the 9130
BSC Evolution as shwon below:
Table 2-1

Telecom Parameters for Definition of Subnet A

Parameter Name

Purpose

Values

IP_Ethernet_Topology

This parameter indicates if


2 LAN topology (with RIP
protocol) or 1 LAN
topology (without RIP
protocol) is used by the
BSC in IP over Ethernet
case

One LAN

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-3
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

O&M and Telecom with one shared subnet

....................................................................................................................................................................................................................................

Table 2-1

Telecom Parameters for Definition of Subnet A

(continued)

Parameter Name

Purpose

Values

IP_Extraction_Point

This parameter indicates


whether the IP link for
OMC-R and CBC is
extracted/inserted directly
at SSW board (BSC), at
the TCADAPT (IP over
Ater) or at the MSC (IP
over Ater). This
information is needed for
programming the
TC-ADAPT

Direct (the extraction point is


the BSC)

BSS_Transport_Mode

This parameter indicates


whether the 9130 BSC
Evolution uses a TDM or
an IP transport on Ater
level

IP transport

EN_ASIG_OVER_IP

This parameter indicates


whether the 9130 BSC
Evolution uses a TDM or
an IP A signalling

True

EN_AUP_OVER_IP

This parameter indicates


wheter the 9130 BSC
Evolution uses a TDM, a
mixed TDM - IP mode or
an IP A User Plane.

True

IP_EXTLINK_ SHARING

Indicates if the O&M link


is shared with a 9130 MFS
Evolution or not.

No

BSC_IP_O&M_SUBNET_
MASK

Gives the mask of the


external subnet A for
O&M

Shall be higher than or equal to


32 hosts (/27 minimum).

START_O&M_IP_
ADDRESSES

Indicates the first IP


address of the range
reserved for the BSC in
Subnet A for O&M

START_ASIG_IP_ADDRESS_
BSC

Start address for the A


Signalling over IP
(ASigoIP) subnet. The
range size is 2

No default value. Shall be equal


to Start_O&M_IP_Address + 2

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-4
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

O&M and Telecom with one shared subnet

....................................................................................................................................................................................................................................

Table 2-1

Telecom Parameters for Definition of Subnet A

(continued)

Parameter Name

Purpose

Values

ASIG_IP_SUBNET_MASK_
BSC

Subnet mask for the A


Signalling over IP
(ASigoIP) subnet.

The minimum range size is 2.


Shall be equal to
BSC_IP_O&M_Subnet_Mask

START2_ASIG_IP_ADDRESS_ Start address for theASig


BSC
over IP: symmetric
Multi-homing subnet. The
range size is 2

No default value. Shall be equal


to Start_O&M_IP_Address + 2

ASIG_IP_SUBNET_MASK2_
BSC

Subnet mask for the ASig


over IP: symmetric
Multi-homing subnet.

The minimum range size is 2.


Shall be equal to
BSC_IP_O&M_Subnet_Mask

START_BSS_IP_ADDRESS_
BSC

Start address for the BSS


over IP (BSSoIP) subnet.
The range size is 10.

No default value. Shall be equal


to Start_O&M_IP_Address + 2

BSS_IP_SUBNET_MASK_
BSC

Subnet mask for the BSS


over IP (BSSoIP) subnet

The range size is 10. Shall be


equal to BSC_IP_O&M_Subnet_
Mask

START_AUP_IP_ADDRESS_
BSC

Start addres for the A User


Plane over IP (AUPoIP)
address range.

No default value. Shall be equal


to Start_O&M_IP_Address + 2

AUP_IP_SUBNET_MASK_
BSC

Subnet mask for the subnet


where A User Plane over
IP (AUPoIP) addresses are
located.

The minimum range size is 3.


Shall be egual to
BSC_IP_O&M_Subnet_Mask

START_ADD_FUNC_
IP_ADDRESS_BSC

Start address for the Lb


and/or Iur-g IP address
range

No default value. Shall be equal


to Start_O&M_IP_Address + 2

ADD_FUNC_IP_
SUBNET_MASK_BSC

Subnet mask for the subnet


where Lb and/or Iur-g IP
addresses are located

The minimum range size is 2.


Shall be equal to
BSC_IP_O&M_Subnet_Mask

VLAN_CONF_INDEX

Allows the selection of the


appropriate internal VLAN
tags to use at BSC switch
level

common tagging

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-5
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

O&M and Telecom with one shared subnet

....................................................................................................................................................................................................................................

Table 2-1

Telecom Parameters for Definition of Subnet A

(continued)

Parameter Name

Purpose

Values

ROUTING_TABLE (BSC)

Defines the list of static


routes. Each route is
defined by :

To define the IP addresses of


the routes towards the gateway
(used by the BSC for sending
IP packets to the external
world)

the destination IP
address

the destination IP
subnet mask

the gateway IP address

For the reachability test, the necessary telecom parameters are set in the 9130 BSC
Evolution, as shown below:.
Table 2-2

The telecom parameters for the reachability test

Parameter Name

Purpose

Values

REACHABILITY_TEST_
ADDR_O&M

IP address to be used by
the BSC for testing the
access to the external
network for O&M needs

Address of the gateway

REACHABILITY_TEST_
ADDR_ASIG

IP Address to be used by
the BSC for testing the
access to the external
network for A Signalling
over IP (AsigoIP) Telecom
needs.

Address of the gateway used


for A Signalling over IP
(AsigoIP) Telecom needs. Same
value as REACHABILITY_TEST_
ADDR_O&M

REACHABILITY_TEST2_
ADDR_ASIG

IP Address to be used by
the BSC for testing the
access to the external
network for ASig over IP:
symmetric Multi-homing
Telecom needs.

Address of the gateway used


for ASig over IP: symmetric
Multi-homing Telecom needs.
Same value as
REACHABILITY_TEST_
ADDR_O&M

REACHABILITY_TEST_
ADDR_BSS

IP Address to be used by
the BSC for testing the
access to the external
network for BSS over IP
(BSSoIP) telecom needs

Address of the gateway used


for BSS over IP (BSSoIP)
Telecom needs. Same value as
REACHABILITY_TEST_
ADDR_O&M

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-6
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

O&M and Telecom with one shared subnet

....................................................................................................................................................................................................................................

Table 2-2

The telecom parameters for the reachability test

(continued)

Parameter Name

Purpose

Values

REACHABILITY_
TEST_ADDR_ ADD_FUNC

IP Address to be used by
the BSC for testing the
access to the external
network for Lb and/or
Iur-g over IP Telecom
needs

Address of the gateway used


for Lb and/or Iur-g over IP
Telecom needs. Same value as
REACHABILITY_
TEST_ADDR_O&M

REACHABILITY_
TEST_ADDR_ AUP

IP Address to be used by
the BSC for testing the
access to the external
network for A User Plane
over IP (AUPoIP) telecom
needs.

Address of the gateway used


for A User Plane over IP
(AUPoIP) Telecom needs.
Same value as
REACHABILITY_
TEST_ADDR_O&M.

To reach the BSC OMCP boards, the Alarm box and the CCP boards from everywhere in
the IP O&M network, the external IP addresses based on the
START_O&M_IP_ADDRESS are set in the 9130 BSC Evolution as shown below:
Table 2-3

The external IP addresses for O&M

Boards

IP Address

9130 BSC Evolution OMCP1

Start_O&M_IP_Address

9130 BSC Evolution OMCP2

Start_O&M_IP_Address + 1

9130 BSC Evolution active OMCP

Start_O&M_IP_Address + 2

9130 BSC Evolution active OMCP standby


plane (for O&M standby plane reachability
test)

Start_O&M_IP_Address + 3

Reserved for spare

Start_O&M_IP_Address + 4

External alarm box

Start_O&M_IP_Address + 12

Reserved for spare

Start_O&M_IP_Address + 6

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-7
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

O&M and Telecom with one shared subnet

....................................................................................................................................................................................................................................

For A Signalling over IP (AsigoIP), to reach the BSC OMCP boards, the Alarm box, the
CCP boards from everywhere in the IP Telecom network, the external IP addresses based
on the START_ASIG_IP_ADDRESS_BSC are set in the 9130 BSC Evolution as shown
below:
Table 2-4

The external IP addresses for A Signalling over IP (AsigoIP)

Boards

IP Address

9130 BSC Evolution active OMCP

Start_Asig_IP_Address_BSC

9130 BSC Evolution active OMCP standby


plane (for Telecom standby plane reachability
test)

Start_Asig_IP_Address_BSC + 1

For ASig over IP: symmetric Multi-homing, to reach the BSC OMCP boards, the Alarm
box, the CCP boards from everywhere in the IP Telecom network, the external IP
addresses based on the START2_ASIG_IP_ADDRESS_BSC are set in the 9130 BSC
Evolution as shown below:
Table 2-5

The external IP addresses for ASig over IP: symmetric Multi-homing

Boards

IP Address

9130 BSC Evolution active OMCP

Start2_Asig_IP_Address_BSC

9130 BSC Evolution active OMCP standby


plane (for Telecom standby plane reachability
test)

Start2_Asig_IP_Address_BSC + 1

For A User Plane over IP (AUPoIP), to reach the BSC OMCP boards and the TPGSM
board, from everywhere in the IP network, the external IP addresses based on the
START_AUP_IP_ADDRESS_BSC are set in the 9130 BSC Evolution as shown below:
Table 2-6

The external IP addresses for A User Plane over IP (AUPoIP)

Boards

IP Address

9130 BSC Evolution


active OMCP

START_AUP_IP_
Address_BSC

9130 BSC Evolution


active OMCP standby
plane (for Telecom
standby plane
reachability test)

START_AUP_IP_
Address_BSC + 1

BSC Parameter

Description

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-8
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

O&M and Telecom with one shared subnet

....................................................................................................................................................................................................................................

Table 2-6

The external IP addresses for A User Plane over IP (AUPoIP)


(continued)

Boards

IP Address

BSC Parameter

Description

9130 BSC Evolution


active TPGSM/TPIP

START_AUP
_IP_Address _BSC +
2

RTP_IP_
ADDRESS_ BSC

RTP_IP_ Address
addresses of the RTP
and MUXRTP TPIP
data path termination.
The RTP function is
supported by the
TPIP (TPGSM).

For BSS over IP (BSSoIP), to reach the BSC OMCP boards, the CCP boards, the TPGSM
from everywhere in the IP Telecom network, the external IP addresses based on the
Start_BSS_IP_Address_BSC, are set in the BSC as shown below:
Table 2-7

The external IP addresses for BSS over IP (BSSoIP)

Boards

IP Address

9130 BSC Evolution active OMCP

Start_BSS_IP_Address_BSC

9130 BSC Evolution active OMCP standby


plane (for standby plane reachability test)

Start_BSS_IP_Address_BSC + 1

9130 BSC Evolution active TPGSM

Start_BSS_IP_Address_BSC + 2

9130 BSC Evolution active CCP 1

Start_BSS_IP_Address_BSC + 3

9130 BSC Evolution active CCP 2

Start_BSS_IP_Address_BSC + 4

9130 BSC Evolution active CCP 3

Start_BSS_IP_Address_BSC + 5

9130 BSC Evolution active CCP 4

Start_BSS_IP_Address_BSC + 6

9130 BSC Evolution active CCP 5

Start_BSS_IP_Address_BSC + 7

9130 BSC Evolution active CCP 6

Start_BSS_IP_Address_BSC + 8

9130 BSC Evolution active CCP 7

Start_BSS_IP_Address_BSC + 9

For LB / Iur-g over IP, to reach the BSC OMCP boards, the Alarm box, the CCP boards
from everywhere in the IP Telecom network, the external IP addresses based on the
Start_Add_Func_IP_Address_BSC, are set in the 9130 BSC Evolution as shown below:
Table 2-8

The external IP addresses for Lb / Iur-g over IP

Boards

IP Address

9130 BSC Evolution active OMCP

Start_Add_Func_IP_Address_BSC

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-9
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

O&M and Telecom with one shared subnet

....................................................................................................................................................................................................................................

Table 2-8

The external IP addresses for Lb / Iur-g over IP

(continued)

Boards

IP Address

9130 BSC Evolution active OMCP standby


plane (for Telecom standby plane reachability
test)

Start_Add_Func_IP_Address_BSC + 1

To change 9130 BSC Evolution IP address plan, refer to Change IP Address Plan, to
Common O&M and Telecom flows in BSC .

Several Subnets for Separate O&M and Telecom


Overview

For the O&M and Telecom transport mode, the following subnets are used, a as shown in
the following figures:

A1 - O&M subnet
A2 - AsigoIP subnet

A3 - BSSoIP subnet
A4 - Lb / Iur-g subnet
A5 - AUPoIP subnet

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-10
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Figure 2-3 9130 BSC Evolution in one LAN configuration with VRRP (O&M, AsigoIP,
BSSoIP, Lb / Iur-g AUPoIP are separated)

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-11
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-12
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Figure 2-4 9130 BSC Evolution in one LAN configuration without VRRP (O&M,
AsigoIP, BSSoIP, Lb / Iur-g and AUPoIP are separated)

For the definition of the subnet A1, refer to the BSS O&M Routing Configurations
document (3BK 17422 5002 PGZZA).

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-13
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

For the definition of the subnet A2, A3, A4 and A5 the necessary telecom parameters are
set in the 9130 BSC Evolution as shown in the following table.
Table 2-9

The telecom parameters for the definition of the subnets

Parameter Name

Purpose

Values

Applicable Subnet

IP_Ethernet_
Topology

This parameter
indicates if 2 LAN
topology (with RIP
protocol) or 1 LAN
topology (without
RIP protocol) is used
by the BSC in IP over
Ethernet case

One LAN

All

IP_Extraction_Point

This parameter
indicates whether the
IP link for OMC-R
and CBC is
extracted/inserted
directly at SSW board
(BSC), at the
TCADAPT (IP over
Ater) or at the MSC
(IP over Ater). This
information is needed
for programming the
TC-ADAPT.

Direct (the extraction


point is the BSC)

All

BSS_Transport_
Mode

This parameter
indicates whether the
9130 BSC Evolution
uses a TDM or an IP
transport on Ater
level.

IP transport

All

IP_EXTLINK_
SHARING

Indicates if the O&M


link is shared with a
9130 MFS Evolution
or not.

No

All

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-14
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Table 2-9

The telecom parameters for the definition of the subnets


(continued)

Parameter Name

Purpose

Values

Applicable Subnet

VLAN_CONF_
INDEX

Allows the selection


of the appropriate
internal VLAN tags
to use at BSC switch
level.

Default value is

All

COMMON TAGGING.

The available values


for this paramater are:

ROUTING_TABLE
(BSC)

COMMON
TAGGING

DISTINC ASIP
AUIP BSS LB
IURG

DISTINCT
ASIP AUIP BSS

DISTINCT OAM
AOIP BSS

DISTINCT OAM
TEL

Defines the list of


static routes. Each
route is defined by :

the destination IP
address

the destination IP
subnet mask

the gateway IP
address

BSC_IP_O&M_Subnet_Gives the mask of the


Mask
external subnet A1
for O&M

Start_O&M_IP_
Address

Indicates the first IP


address of the range
reserved for the BSC
in Subnet A for O&M

To define the IP
addresses of the
Routes towards the
gateway (used by the
BSC for sending IP
packets to the
external world)

All

Shall be higher than


or equal to 6 hosts.
Default value:
255.255.255.248 for
6 hosts (/29 as prefix
network)

A1

A1

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-15
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Table 2-9

The telecom parameters for the definition of the subnets


(continued)

Parameter Name

Purpose

Values

Applicable Subnet

REACHABILITY_
TEST_ADR_O&M

IP address to be used
by the BSC for
testing the access to
the external network
for O&M needs

IP address of the
gateway used for
O&M

A1

EN_ASIG_OVER_IP

This parameter
indicates whether the
9130 BSC Evolution
uses a TDM or an IP
A signalling.

True

A2

START_ASIG_IP_
ADDRESS_BSC

Start address for the


A Signalling over IP
(AsigoIP) subnet. The
range size is 2

ASIG_IP_SUBNET_
MASK_BSC

Subnet mask for the


A Signalling over IP
(AsigoIP) subnet.

The minimum range


size is 2

A2.1

REACHABILITY_
TEST_ADDR_ASIG

IP Address to be used
by the BSC for
testing the access to
the external network
for A Signalling over
IP (AsigoIP) Telecom
needs

Address of the
gateway used for A
Signalling over IP
(AsigoIP) Telecom
needs

A2.1

START2_ASIG_IP_
ADDRESS_BSC

Start address for the


ASig over IP:
symmetric
Multi-homing subnet.
The range size is 2

ASIG_IP_SUBNET_
MASK2_BSC

Subnet mask for the


ASig over IP:
symmetric
Multi-homing subnet.

A2.1

A2.2

The minimum range


size is 2

A2.2

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-16
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Table 2-9

The telecom parameters for the definition of the subnets


(continued)

Parameter Name

Purpose

Values

Applicable Subnet

REACHABILITY_
TEST2_ADDR_
ASIG

IP Address to be used
by the BSC for
testing the access to
the external network
for the ASig over IP:
symmetric
Multi-homing
Telecom needs

Address of the
gateway used for
ASig over IP:
symmetric
Multi-homing
Telecom needs

A2.2

BSS_IP
_SUBNET_MASK
_BSC

Subnet mask for the


BSS over IP
(BSSoIP) subnet.

The range size is 10

A3

START_BSS
_IP_ADDRESS
_BSC

Start address for the


BSS over IP
(BSSoIP) subnet. The
range size is 10

REACHABILITY_
TEST_ADDR_ BSS

IP Address to be used
by the BSC for
testing the access to
the external network
for BSS over IP
(BSSoIP) telecom
needs

Address of the
gateway used BSS
over IP (BSSoIP)
Telecom needs

A3

EN_LB

Indicates whether
Mx-BSC enable Lb
interface

TRUE

A4

EN_IURG

Indicates whether
Mx-BSC enable Iur-g
interface

TRUE

A4

A3

A4

START_ADD_FUNC_ Start address for the


IP_ADDRESS_BSC
Lb and/or Iur-g
address range
ADD_FUNC_IP_
SUBNET_MASK_
BSC

Subnet mask for the


subnet where Lb
and/or Iur-g addresses
are located

The minimum range


size is 2

A4

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-17
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Table 2-9

The telecom parameters for the definition of the subnets


(continued)

Parameter Name

Purpose

Values

Applicable Subnet

REACHABILITY_
TEST_
ADDR_ADD_FUNC

IP Address to be used
by the BSC for
testing the access to
the external network
for Lb and/or Iur-g
over IP Telecom
needs

Address of the
gateway used for Lb
and/or Iur-g over IP
Telecom needs

A4

START_AUP_IP_
ADDRESS_BSC

First IP address for


the range of telecom
addresses shown to
the external world for
the feature A User
Plane over IP
(AUPoIP).

AUP_IP_SUBNET_
MASK_BSC

Mask of the subnet


where is allocated the
range of BSC
addresses used for
telecom protocols for
the feature A User
Plane over IP.

The minimum range


size is 3

A5

REACHABILITY_
TEST_ADDR_AUP

The IP address to be
used by the BSC for
testing the access to
the external network
for A User Plave over
IP (AUPoIP) telecom
needs. It has to be in
the same subnet as
BSC Start AUP over
IP Address.

Address of the
gateway used for A
User Plane over IP
Telecom (AUPoIP)
needs

A5

EN_AUP_OVER_IP

This parameter
indicates whether the
9130 BSC Evolution
uses an TDM or an IP
A User Plane
transport.

TRUE

A5

A5

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-18
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

In subnet A1, to reach the BSC OMCP boards and the Alarm box from everywhere in the
IP O&M network, the external IP addresses based on the START_O&M_IP_ADDRESS
are set in the 9130 BSC Evolution as shown in the following table.
Table 2-10

The external IP addresses for O&M

Boards

IP Address

9130 BSC Evolution OMCP1

Start_O&M_IP_Address

9130 BSC Evolution OMCP2

Start_O&M_IP_Address + 1

9130 BSC Evolution active OMCP

Start_O&M_IP_Address + 2

9130 BSC Evolution active OMCP standby


plane (for O&M standby plane reachability
test)

Start_O&M_IP_Address + 3

Reserved for spare

Start_O&M_IP_Address + 4

External alarm box

Start_O&M_IP_Address + 5

Reserved for spare

Start_O&M_IP_Address + 6

For A Signaling over IP (AsigoIP), to reach the BSC OMCP boards from everywhere in
the IP network, the external IP addresses based on the START_ASIG_IP_ADDRESS_BSC are set in the 9130 BSC Evolution as shown below:
Table 2-11

The external IP addresses for A Signaling over IP (AsigoIP)

Boards

IP Address

9130 BSC Evolution active OMCP

Start_Asig_IP_Address_BSC

9130 BSC Evolution active OMCP standby


plane (for Telecom standby plane reachability
test)

Start_Asig_IP_Address_BSC + 1

For ASig over IP: symmetric Multi-homing, to reach the BSC OMCP boards from
everywhere in the IP network, the external IP addresses based on the
START2_ASIG_IP_ADDRESS_BSC are set in the 9130 BSC Evolution as shown below:
Table 2-12

The external IP addresses for ASig over IP: symmetric Multi-homing


for AsigoIP

Boards

IP Address

9130 BSC Evolution active OMCP

Star2t_Asig_IP_Address_BSC

9130 BSC Evolution active OMCP standby


plane (for Telecom standby plane reachability
test)

Start2_Asig_IP_Address_BSC + 1

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-19
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

For A User Plane over IP (AUPoIP), to reach the BSC OMCP boards and the TPGSM
board from everywhere in the IP network, the external IP addresses based on the
START_AUP_IP_ADDRESS_BSC are set in the 9130 BSC Evolution as shown below:
Table 2-13

The external IP addresses for A User Plane over IP (AUPoIP)

Boards

IP Address

9130 BSC Evolution


active OMCP

START_AUP_IP_
Address_BSC

9130 BSC Evolution


active OMCP standby
plane (for Telecom
standby plane
reachability test)

START_AUP_IP_
Address_BSC + 1

9130 BSC Evolution


active TPGSM/TPIP

START_AUP_IP_
Address_BSC + 2

BSC Parameter

Description

RTP_IP_
ADDRESS_BSC

RTP_IP_ Address
addresses of he RTP
and MUXRTP TPIP
data path termination.
The RTP function is
supported by the
TPIP (TPGSM)

For BSS over IP (BSSoIP), to reach the BSC OMCP boards, the CCP boards, the TPGSM
from everywhere in the IP network, the external IP addresses based on the
Start_BSS_IP_Address_BSC, are set in the BSC as shown below:
Table 2-14

The external IP addresses for BSS over IP (BSSoIP)

Boards

IP Address

9130 BSC Evolution active OMCP

Start_BSS_IP_Address_BSC

9130 BSC Evolution active OMCP standby


plane (for standby plane reachability test)

Start_BSS_IP_Address_BSC + 1

9130 BSC Evolution active TPGSM

Start_BSS_IP_Address_BSC + 2

9130 BSC Evolution active CCP 1

Start_BSS_IP_Address_BSC + 3

9130 BSC Evolution active CCP 2

Start_BSS_IP_Address_BSC + 4

9130 BSC Evolution active CCP 3

Start_BSS_IP_Address_BSC + 5

9130 BSC Evolution active CCP 4

Start_BSS_IP_Address_BSC + 6

9130 BSC Evolution active CCP 5

Start_BSS_IP_Address_BSC + 7

9130 BSC Evolution active CCP 6

Start_BSS_IP_Address_BSC + 8

9130 BSC Evolution active CCP 7

Start_BSS_IP_Address_BSC + 9

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-20
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

To reach the BSC OMCP boards, the Alarm box, the CCP boards from everywhere in the
IP Telecom network, the external IP addresses based on the Start_Add_Func_IP_Address_BSC, are set in the 9130 BSC Evolution as shown in the following table.
Table 2-15

The external IP addresses for Lb / Iur-g over IP

Boards

IP Address

9130 BSC Evolution active OMCP

Start_Add_Func_IP_Address_BSC

9130 BSC Evolution active OMCP standby


plane (for Telecom standby plane reachability
test)

Start_Add_Func_IP_Address_BSC + 1

The 9130 BSC Evolution flows and switch ports to be used are shown in the following
table.
Note: In IP BSS, the allowed configurations are VLAN Conf Index: 0, 1, 2, 3 or 4.
In TDM BSS, the allowed configurations are VLAN Conf Index: 0 or 1 (there is no
MUXtraup).
Table 2-16

The 9130 BSC Evolution flow and switch ports

VLAN_
CONF _
INDEX

IP Addr.
Used

9130 BSC Evolution switch ports

9130 BSC Evolution flows separation


0

12

O&M +
Telecom

Aflex-TDM
O&M
possibility

14

O&M

Telecom

Aflex-TDM
O&M
possibility

17

O&M

AoIP
(AsigoIP
and
AUPoIP)

BSSoIP /
Lb / Iur-g

19

O&M

AsigoIP

AUPoIP

BSSoIP /
Lb / Iur-g

21

O&M

AsigoIP

AUPoIP

BSSoIP

Lb /
Iur-g

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-21
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

To change 9130 BSC Evolution IP address plan use, refer to the following table.
Table 2-17

VLAN Conf Index description

VLAN Conf Index number

VLanc Conf Index Parameter

COMMON TAGGING

DISTINCT OAM TEL

DISTINCT OAM AOIP BSS

DISTINCT ASIP AUIP BSS

DIST ASIP AUIP BSS LB IURG

Reachability Test
Overview

The BSC performs a reachability test on:

O&M address (REACHABILITY_TEST_ADDR_O&M)


Several telecom addresses (REACHABILITY_TEST_ADDR_BSS,
REACHABILITY_TEST_ADDR_ASIG, REACHABILITY_TEST2_ADDR_ASIG,
REACHABILITY_TEST_ADDR_AUP)

In order to have an efficient test, the reachability address shall be the first address
encountered out of the BSC for the O&M, Asig over IP or BSS over IP flows.
The test is performed by the active OMCP on both active and standby switch sides for the
O&M and telecom reachability test addresses.
Both O&M and telecom use the same switch plane.
If the telecom over IP feature is activated arm a telecom related timer, or arm an O&M
related timer if the feature is not activated.
When telecom timer elapses:
Case 1 : Telecom addresses are different from O&M address:
Test telecom address and O&M addresses on both active/standby sides:

Case: 'failure of at least a telecom active side' then swap to the other switch side if
working and send an alarm
Case: 'failure of at least a telecom standby side' then send an alarm.
Case: 'failure of O&M active side' then swap to the other switch side if standby side is
ok for telecom and send an alarm
Case: 'failure of O&M standby side' then send an alarm

Case 2 : O&M address is identical to at least one telecom address:


....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-22
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Reachability Test

....................................................................................................................................................................................................................................

Test telecom address on both active/standby sides:

Case 'failure of at least a telecom active side' then swap to the other switch side if
working and send an alarm
Case 'failure of at least a telecom standby side' then only send an alarm.

Arm a telecom related timer.


By 'failure of telecom active/standby side' is to be understood unable to reach the telecom
address for reachability test when using the active/standby side.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-23
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 BSC Evolution

Reachability Test

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
2-24
3MN-01075-1873-PGZZA
Issue 6 November 2012

I3P Transport Management


in 9130 MFS Evolution

Overview
Purpose

This section is dedicated to the IP addressing of the 9130 MFS Evolution subsystem.
Contents
LAN Configuration

3-1

IP Addressing Rules

3-2

Several Subnets for Separate O&M and Telecom

3-2

Reachability Test

3-11

O&M Reachability Test

3-12

Telecom Reachability Test by Control Station

3-14

Telecom Reachability Test by the GPU

3-16

Reachability Test Rules

3-18

LAN Configuration
Overview

Telecom over IP features are only supported in one LAN topology.

...................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-1
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

IP Addressing Rules

....................................................................................................................................................................................................................................

IP Addressing Rules
Overview

IP addresses for a 9130 MFS Evolution can be chosen freely, limited only by the
following rules:
9130 MFS Evolution external addresses must not belong to the following networks:

172.16/16, 172.17/16, 172.18/16, 172.19/16, 172.32/16


192.168.<SGA>.65, 192.168.<SGA>.66 where <SGA> means Shelf Geographical
Address and can have the value 3 or 4.

OMC-Rs or other equipment with which the 9130 MFS Evolution interacts must not
belong to the following networks:

172.16/16, 172.17/16, 172.18/16, 172.19/16, 172.32/16

192.168.<SGA>.65, 192.168.<SGA>.66 where <SGA> means Shelf Geographical


Address and can have the value 3 or 4
Customer is free to use these networks, provided these networks or machines on this
network do not interact with 9130 MFS Evolution.

Several Subnets for Separate O&M and Telecom


Overview

The Telecom flows are the following:

Gb over IP on Gb interface with SGSN


GSL over IP on Ater interface with the BSC
IPGCH over IP on Ater interface with the BTS

At most, one subnet for O&M flow and one subnet for each Telecom flow are permitted,
as shown in the following figure.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-2
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Note: The O&M interface on the existing access router can also be configured for the
telecom flow.
Other possible Telecom subnets configurations:

Two subnets:
As follows:
O&M subnet
Telecom subnet (with all the Telecom flows)
Three subnets:
As follows:
O&M subnet
Gb subnet
BSS subnet (IPGSL and IPGCH functions)
Four subnets:

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-3
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

As follows:
O&M subnet
Gb subnet

IPGSL subnet
IPGCH subnet

If one of the Telecom function is not activated in IP, the following configurations are
possible:

Gb in TDM and BSS in IP (IPGSL or IPGCH or both in IP)


Two subnets:
O&M subnet
BSS subnet (IPGSL or IPGCH flows or both)
BSS in TDM (GSL or IPGCH or both) and Gb in IP

The necessary parameters for this LAN configuration are set in the 9130 MFS Evolution
as shown in the following table.
Table 3-1

Parameters for LAN Configuration

Parameter Name

Purpose

Values

Enable RIPv2

Indicates whether a one


LAN (no RIP) or two
LAN (RIP) solution is
used

No

ROUTING_TABLE (MFS)

Defines the list of static


routes. Each route is
defined by: the destination
IP address, the destination
IP subnet mask, the
gateway IP address

IP addresses of the routes


towards the gateway

VLAN_CONF_INDEX (MFS)

Allows the selection of the


appropriate internal VLAN
tags to use at MFS SW
level

Default value is 0 - common


O&M / telecom tagging.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-4
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

The MFS flows and switch ports to be used are as follows.


Table 3-2

MFS Flow and Switch Ports

VLAN_CONF
_INDEX (MFS)
3

MFS flows separation


0

O&M + Telecom

O&M

Telecom

O&M

GboIP

BSSoIP

O&M

GboIP

IPGSL

IPGCH

For the definition of the subnet A, the necessary O&M parameters are set in the 9130
MFS Evolution as shown below:
Table 3-3

Telecom Parameters for Definition of Gb Subnet

Parameter Name

Purpose

MFS_IP _Address

IP address to be used by
OMC-R to reach the MFS.
Set from OMC-R.

Netmask floating address

Gives the mask of the


external subnet for O&M
9130 MFS Evolution

REACHABILITY_TEST_
ADDR_O&M

IP address to be used by
the 9130 MFS Evolution
for testing the access to the
external network for O&M
needs

Values

For the definition of the subnet Gb, the necessary telecom parameters are set in the 9130
MFS Evolution as shown in the following table.
Table 3-4

Telecom Parameters for Definition of Gb Subnet

Parameter Name

Purpose

GB_Transport_ Mode

Indicates whether the


telecom function uses a
TDM or IP transport on
Gb

Values

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-5
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Table 3-4

Telecom Parameters for Definition of Gb Subnet

(continued)

Parameter Name

Purpose

Values

IPGB_SUBNET_MASK_MFS

Gives the mask of the


external subnet from
O&M 9130 MFS
Evolution

Should be higher or equal to 32


hosts (>-/27)
Default value: 255.255.255.224

REACHABILITY_TEST_ADR_ IP address to be used by


TEL _GB(MFS)
the 9130 MFS Evolution
for testing the access to the
external network for Gb
flow needs
REACHABILITY_
TEST_ADDR_ TEL_GB_GPU

IP address to be used by
the GPU for testing the
access to the external
network for Gb telecom
needs.

Use the following table to obtain the GPU IP addresses in the Gb subnet (in this example
GB_Gb_Base_IP is 10.102.111.193).
Table 3-5

IP-Adressing Inside MFS for Gb-over-IP Table

No.

Example IP
Address (/27
subnet)

Automated IP
Address
Allocation

GPU Logical
Numbering

Comment /
Options

10.102.111.192

subnet IP address

10.102.111.193

GPU_GB_Base_IP
+0

GPU 1

GPU_Gb_Base_IP

10.102.111.194

GPU_GB_Base_IP
+1

GPU 2

10.102.111.195

GPU_GB_Base_IP
+2

GPU 3

10.102.111.196

GPU_GB_Base_IP
+3

GPU 4

10.102.111.197

GPU_GB_Base_IP
+4

shall be kept free


for spare

10.102.111.198

GPU_GB_Base_IP
+5

10.102.111.199

GPU_GB_Base_IP
+6

possible Gateway
IP Address

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-6
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Table 3-5

IP-Adressing Inside MFS for Gb-over-IP Table

(continued)

No.

Example IP
Address (/27
subnet)

Automated IP
Address
Allocation

GPU Logical
Numbering

Comment /
Options

10.102.111.200

GPU_GB_Base_IP
+7

possible Gateway
IP Address

10.102.111.201

GPU_GB_Base_IP
+8

10

10.102.111.202

GPU_GB_Base_IP
+9

GPU 10

11

10.102.111.203

GPU_GB_Base_IP
+ 10

GPU 11

12

10.102.111.204

GPU_GB_Base_IP
+ 11

GPU 12

13

10.102.111.205

GPU_GB_Base_IP
+ 12

GPU 13

14

10.102.111.206

GPU_GB_Base_IP
+ 13

GPU 14

15

10.102.111.207

GPU_GB_Base_IP
+ 14

GPU 17

16

10.102.111.208

GPU_GB_Base_IP
+ 15

GPU 18

17

10.102.111.209

GPU_GB_Base_IP
+ 16

GPU 19

18

10.102.111.210

GPU_GB_Base_IP
+ 17

GPU 20

19

10.102.111.211

GPU_GB_Base_IP
+ 18

GPU 21

20

10.102.111.212

GPU_GB_Base_IP
+ 19

GPU 22

21

10.102.111.213

GPU_GB_Base_IP
+ 20

possible Gateway
IP Address

22

10.102.111.214

GPU_GB_Base_IP
+ 21

possible Gateway
IP Address

23

10.102.111.215

GPU_GB_Base_IP
+ 22

GPU 25

24

10.102.111.216

GPU_GB_Base_IP
+ 23

GPU 26

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-7
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Table 3-5

IP-Adressing Inside MFS for Gb-over-IP Table

(continued)

No.

Example IP
Address (/27
subnet)

Automated IP
Address
Allocation

GPU Logical
Numbering

Comment /
Options

25

10.102.111.217

GPU_GB_Base_IP
+ 24

GPU 27

26

10.102.111.218

GPU_GB_Base_IP
+ 25

GPU 28

27

10.102.111.219

GPU_GB_Base_IP
+ 26

GPU 29

28

10.102.111.220

GPU_GB_Base_IP
+ 27

GPU 30

29

10.102.111.221

not used

30

10.102.111.222

Hostaddress for
HSRP

31

10.102.111.223

broadcast

Note: The Gateway IP address allocation:


For the upper shelf, is one of the following:

GPU_Gb_Base_IP + 6
GPU_Gb_Base_IP + 7

For the lower shelf, is one of the following:

GPU_Gb_Base_IP + 20

GPU_Gb_Base_IP + 21

For the definition of the subnet BSS/IPGSL, the necessary telecom parameters are set in
the 9130 MFS Evolution as shown in the following table.
Table 3-6

Telecom Parameters for Definition of BSS/IPGSL Subnet

Parameter Name

Purpose

Values

BSS_Transport _Mode (MFS)

Indicates whether MFS


uses a TDM or an IP
transport on GSL level and
IPGCH

IP transport

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-8
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Table 3-6

Telecom Parameters for Definition of BSS/IPGSL Subnet

(continued)

Parameter Name

Purpose

Values

IPBSS_SUBNET
_MASK_MFS

Gives the mask of the


external subnet for BSS
Telecom (IPGCH/GSL)
9130 MFS Evolution
address.

Should be higher or equal to 32


host (>=27)

IPGSL_Base _Address_MFS

Default value: 255.255.255.224

Starting GPU IPGSL


address.

REACHABILITY_TEST_ADDR_IP address to be used by


TEL_GSL
the 9130 MFS Evolution
for testing the access to the
external network for
IPGSL telecom needs
REACHABILITY_
TEST_ADDR_TEL_GSL_
GPU

P address to be used by the


GPU for testing the access
to the external network for
IP GSL telecom needs.

Use the formula shown in the following table to obtain the GPU IP addresses in the
corresponding BSS/IPGSL subnet.
Table 3-7

IP Assignment Rules in BSS/IPGSL Subnet

Configuration

GPU IP address

9 GPU

IPGSL_Base_Address_MFS + Y 1
Where Y is the GPU physical slot number

16 GPU or 21 GPU

IPGSL_Base_Address_MFS + (X 3) * 14 +
Y1
Where

X is the geographical shelf address

Y is the GPU logical slot number

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-9
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

For the definition of the subnet BSS/IPGCH, the necessary telecom parameters are set in
the 9130 MFS Evolution as shown below:
Table 3-8

Telecom Parameters for Definition of BSS/IPGCH Subnet

Parameter Name

Purpose

Values

BSS_Transport_ Mode

Indicates whether MFS


uses a TDM or an IP
transport on GSL level and
IPGCH

IP transport

IPBSS_SUBNET
_MASK_MFS

Gives the mask of the


external subnet for BSS
Telecom (IPGCH/GSL)
9130 MFS Evolution
address.

Should be higher or equal to 32


hosts (>= /27)

IPGCH_Base_Address_MFS

Default value: 255.255.255.224

Starting GPU IPGCH


address.

REACHABILITY_TEST_ADDR_IP address to be used by


IPGCH
the 9130 MFS Evolution
for testing the access to the
external network for
IPGCH telecom needs.
REACHABILITY_TEST_ADDR_IP address to be used by
IPGCH_GPU
the GPU for testing the
access to the external
network for IPGCH
telecom needs.

Use the formula shown in the following table toobtain the GPU IP addresses in the
corresponding BSS/IPGCH subnet.
Table 3-9

IP Assignment Rules in BSS/IPGCH Subnet

Configuration

GPU IP address

9 GPU

IPGCH_Base_Address_MFS + Y 1
Where Y is the GPU physical slot number

16 GPU or 21 GPU

IPGCH_Base_Address_MFS + (X 3) * 14 +
Y1
Where

X is the geographical shelf address

Y is the GPU logical slot number

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-10
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Several Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................

Each host in the MFS (control stations and GPUs) must get routing information: gateway
addresses (there can be one gateway per subnet used) and associated subnet. The control
stations have to distribute the information to each GPU (active and spare).
The MFS routing table is configured from the IMT.
To change 9130 MFS IP address plan, refer to Change IP Address Plan, to 9130 MFS
Evolution IP addressing plan change.

Reachability Test
Overview

In order to have an efficient test, the reachability address should be the first address
encountered out of the MFS for the O&M, Gb, IPGSL or IPGCH flow. The farther the
address, the higher the risk to uselessly change the Ethernet plan (higher probability for
failure beyond the edge switch/router, making the change of Ethernet plane inefficient).
To test the reachability for the different physical links, set the following parameters
according to the Reachability Test Rules (p. 3-18) :

REACHABILITY_TEST_ADDR_O&M (MFS), to be used by the active control


stations board for testing the access to the external network for O&M needs; please
refer to O&M Reachability Test (p. 3-12)

REACHABILITY_TEST_ADDR_TEL_GB (MFS), REACHABILITY_TEST_ADDR_TEL_GSL (MFS), REACHABILITY_TEST_ADDR_TEL_IPGCH (MFS), to be


used by the active control station for testing the access to the external network for
telecom needs; please refer to Telecom Reachability Test by Control Station
(p. 3-14)
REACHABILITY_TEST_ADDR_TEL_GB_GPU (MFS), REACHABILITY_TEST_ADDR_TEL_GSL_GPU (MFS), REACHABILITY_TEST_ADDR_TEL_IPGCH_GPU (MFS), to be used by every active GPU for defense of telecom traffic to the
external network for telecom needs; please refer to Telecom Reachability Test by the
GPU (p. 3-16)
REACHABILITY_ PERIODICITY (optional).

In the following sections the reachability IP addresses are described in two ways:

from a L2 network perspective, where the device for which the reachability is tested is
in the same network with the target
from a L3 network perspective, where the device for which the reachability is tested is
not in the same network with the target

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-11
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

O&M Reachability Test

....................................................................................................................................................................................................................................

O&M Reachability Test


How to Test the Access to the External Network for O&M Needs

The test purpose is to manage the Ethernet plan by switching the active / standby plans in
the case of active plan failure.
Both active and standby sides are supervised and associated alarms sent. The standby plan
is supervised to allow standby plan repair before a possible failure of the active plan. The
alarm indicates the concerned control station board and switch plane. An active switch
side failure is detected via the arp cache expiration (one minute, by default). If both
switch sides are down for the active control station, a switchover is not performed since
the associated alarm would not be correctly managed.
Recommended rules:

In order to have an efficient test, the reachability address can be the first address
encountered out of the MFS for the O&M flow

In the case of L3 network, the edge router can have an address in the O&M subnet
It is not necessary to configure more than one reachability test address (tested by
Control Station) per physical link between the MFS and the edge switch / router.

Table 3-10

O&M Reachability Test Address

Parameter Name

L2 Network

REACHABILITY_TEST _ADDR_ The IP address of the


OMC
O&M (MFS)

L3 Network
The IP address of the router
O&M interface

Note: The address is not tested in the case of a 0.0.0.0 value.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-12
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

O&M Reachability Test

....................................................................................................................................................................................................................................

Figure 3-1 9130 MFS Evolution O&M Reachability Test

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-13
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Telecom Reachability Test by Control Station

....................................................................................................................................................................................................................................

Telecom Reachability Test by Control Station


How to Test the Access to the External Network for Telecom Needs

The test of the telecom reachability address used by the control station is done for
supervision requirements. Both active and standby sides are supervised and associated
alarms are . The alarm indicates the concerned control station board and switch plane. A
failure on telecom address does not lead to the control station swap to the other switch
side.
The control station has an IP address in every telecom subnet.
Recommended rules:

In order to have an efficient test, the reachability address can be the first address
encountered out of the MFS for the telecom flow
In the case of L3 network, the edge router can have an address in every telecom
subnet
It is not necessary to configure more than one reachability test address (tested by
Control Station) per physical link between the MFS and the edge switch / router.
Attention: REACHABILITY_TEST_ADDR_TEL_GB (MFS) cannot be configured
when GPU_Gb_Base_IP is not configured
REACHABILITY_TEST_ADDR_TEL_GSL (MFS) cannot be configured when
IPGSL_Base_Address_MFS is not configured
REACHABILITY_TEST_ADDR_TEL_IPGCH (MFS) cannot be configured when
IPGCH_Base_Address_MFS is not configured.

Table 3-11

Control Station Telecom Reachability Test Address

Parameter Name

L2 Network

L3 Network

REACHABILITY_ TEST_
ADDR_ TEL_GB (MFS)

The IP address of one


SGSN

The IP address of the Gb over


IP interface of the router

REACHABILITY_ TEST_
ADDR_ TEL_GSL (MFS)

The telecom IP address of


the BSC

The IP address of the IPGSL


interface of the router

REACHABILITY_ TEST_
ADDR_ TEL_IPGCH (MFS)

The first IP address


encountered out of the
MFS for the IPGCH flow

The IP address of the IPGCH


interface of the router

Note: The address is not tested in the case of a 0.0.0.0 value.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-14
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Telecom Reachability Test by Control Station

....................................................................................................................................................................................................................................

Figure 3-2 9130 MFS Evolution Telecom Reachability Test by Control Station

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-15
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Telecom Reachability Test by the GPU

....................................................................................................................................................................................................................................

Telecom Reachability Test by the GPU


How to Test the Defense of Telecom Traffic to the External Network for Telecom Needs by the
GPU

The test of the telecom reachability address used by the GPU is done for traffic defence
purpose on its active side. The GPU is able to swap to the standby side if needed. If both
sides are down, the GPU alarms.
Each GPU is independent in terms of switching side decision.
Recommended rules:

In order to have an efficient test, the reachability address can be the first address
encountered out of the MFS for the telecom flow
In the case of L3 network, the edge router can have an address in every telecom
subnet
Attention: REACHABILITY_TEST_ADDR_TEL_GB_GPU (MFS) cannot be
configured when GPU_Gb_Base_IP is not configured
REACHABILITY_TEST_ADDR_TEL_GSL_GPU (MFS) cannot be configured when
IPGSL_Base_Address_MFS is not configured
REACHABILITY_TEST_ADDR_TEL_IPGCH_GPU (MFS) cannot be configured when
IPGCH_Base_Address_MFS is not configured.

Table 3-12

GPU Telecom Reachability Test Address

Parameter Name

L2 Network

L3 Network

REACHABILITY_ TEST_
ADDR_ TEL_GB_GPU (MFS)

The IP address of one


SGSN

The IP address of the Gb over


IP interface of the router

REACHABILITY_ TEST_
ADDR_ TEL_GSL_GPU (MFS)

The telecom IP address of


the BSC

The IP address of the IPGSL


interface of the router

REACHABILITY_ TEST_
ADDR_ TEL_IPGCH_GPU
(MFS)

The first IP address


encountered out of the
MFS for the IPGCH flow

The IP address of the IPGCH


interface of the router

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-16
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Telecom Reachability Test by the GPU

....................................................................................................................................................................................................................................

Figure 3-3 9130 MFS Evolution Telecom reachability Test by GPU

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-17
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Reachability Test Rules

....................................................................................................................................................................................................................................

Reachability Test Rules


Reachability Test Rules

Depending on the following topology, set the reachability parameters:

No Flow Separation (p. 3-18)

O&M and Telecom Flows Separation (p. 3-18)

O&M, Gb and BSS Flows Separation (p. 3-19)


Full Flows Separation (p. 3-20)

No Flow Separation

Set at least one of the four parameters used by the Control Station:

REACHABILITY_ TEST_ADDR_ O&M (MFS) and optional,


REACHABILITY_ TEST_LABEL_ O&M (MFS)

If GB over IP is activated, REACHABILITY_ TEST_ADDR_ TEL_GB (MFS) and,


optional, REACHABILITY_ TEST_LABEL_ TEL_GB (MFS)
If BSS over IP is activated,REACHABILITY_ TEST_ADDR_ TEL_GSL (MFS) and,
optional, REACHABILITY_ TEST_LABEL_ TEL_GSL (MFS)
If BSS over IP is activated, REACHABILITY_ TEST_ADDR_ TEL_IPGCH (MFS)
and, optional, REACHABILITY_ TEST_LABEL_ TEL_IPGCH (MFS)

Set the following parameters used by the GPU:

If GB over IP is activated, set


REACHABILITY_ TEST_ADDR_ TEL_GB_GPU (MFS) and, optional,
REACHABILITY_ TEST_LABEL_ TEL_GB_GPU (MFS)

If BSS over IP is activated


Set at least one of the following:
REACHABILITY_ TEST_ADDR_ TEL_GSL_GPU (MFS) and, optional,
REACHABILITY_ TEST_LABEL_ TEL_GSL_GPU (MFS)

or REACHABILITY_ TEST_ADDR_ TEL_IPGCH_GPU (MFS) and, optional,


REACHABILITY_ TEST_LABEL_ TEL_IPGCH_GPU (MFS)

Set the VLAN_CONF_INDEX parameter to 0.


O&M and Telecom Flows Separation

Attention: This topology is valid only if GB over IP or BSS over IP are activated.
Set REACHABILITY_ TEST_ADDR_ O&M (MFS) and optional, REACHABILITY_
TEST_LABEL_ O&M (MFS).

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-18
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Reachability Test Rules

....................................................................................................................................................................................................................................

Set at least one of the parameters below used by the Control Station :

If GB over IP is activated, set REACHABILITY_ TEST_ADDR_ TEL_GB (MFS) and,


optional, REACHABILITY_ TEST_LABEL_ TEL_GB (MFS)
If BSS over IP is activated, set REACHABILITY_ TEST_ADDR_ TEL_GSL (MFS)
and, optional, REACHABILITY_ TEST_LABEL_ TEL_GSL (MFS)
If BSS over IP is activated, set REACHABILITY_ TEST_ADDR_ TEL_IPGCH (MFS)
and, optional, REACHABILITY_ TEST_LABEL_ TEL_IPGCH (MFS)

Set the following parameters used by the GPU :

If GB over IP is activated, set


REACHABILITY_ TEST_ADDR_ TEL_GB_GPU (MFS) and, optional,
REACHABILITY_ TEST_LABEL_ TEL_GB_GPU (MFS)

If BSS over IP is activated


Set at least one of the following:
REACHABILITY_ TEST_ADDR_ TEL_GSL_GPU (MFS) and, optional,
REACHABILITY_ TEST_LABEL_ TEL_GSL_GPU (MFS)

or REACHABILITY_ TEST_ADDR_ TEL_IPGCH_GPU (MFS) and, optional,


REACHABILITY_ TEST_LABEL_ TEL_IPGCH_GPU (MFS)

Set the VLAN_CONF_INDEX parameter to 1.


O&M, Gb and BSS Flows Separation

Attention: This topology is valid only if GB over IP and BSS over IP are activated.
Set REACHABILITY_ TEST_ADDR_ O&M (MFS) and optional, REACHABILITY_
TEST_LABEL_ O&M (MFS).
Set REACHABILITY_ TEST_ADDR_ TEL_GB (MFS) and optional, REACHABILITY_
TEST_LABEL_ TEL_GB (MFS).
Set REACHABILITY_ TEST_ADDR_ TEL_GB_GPU (MFS) and optional,
REACHABILITY_ TEST_LABEL_ TEL_GB_GPU (MFS)

Set at least one of the parameters below used by Control Station :

REACHABILITY_ TEST_ADDR_ TEL_GSL (MFS) and optional,


REACHABILITY_ TEST_LABEL_ TEL_GSL (MFS)

REACHABILITY_ TEST_ADDR_ TEL_IPGCH (MFS) and optional,


REACHABILITY_ TEST_LABEL_ TEL_IPGCH (MFS)

Set at least one of the following parameters used by GPU :

REACHABILITY_ TEST_ADDR_ TEL_GSL_GPU (MFS) and optional,


REACHABILITY_ TEST_LABEL_ TEL_GSL_GPU (MFS)

REACHABILITY_ TEST_ADDR_ TEL_IPGCH_GPU (MFS) and optional,


REACHABILITY_ TEST_LABEL_ TEL_IPGCH_GPU (MFS)

Set the VLAN_CONF_INDEX parameter to 2.


....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-19
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9130 MFS Evolution

Reachability Test Rules

....................................................................................................................................................................................................................................

Full Flows Separation

Attention: This topology is valid only if GB over IP and BSS over IP are activated.
Set the following parameters used by the Control Station :

REACHABILITY_ TEST_ADDR_ O&M (MFS) and optional,


REACHABILITY_ TEST_LABEL_ O&M (MFS)

REACHABILITY_ TEST_ADDR_ TEL_GB (MFS) and, optional,


REACHABILITY_ TEST_LABEL_ TEL_GB (MFS)

REACHABILITY_ TEST_ADDR_ TEL_GSL (MFS) and, optional,


REACHABILITY_ TEST_LABEL_ TEL_GSL (MFS)

REACHABILITY_ TEST_ADDR_ TEL_IPGCH (MFS) and, optional,


REACHABILITY_ TEST_LABEL_ TEL_IPGCH (MFS)

Set the following parameters used by the GPU :

REACHABILITY_ TEST_ADDR_ TEL_GB_GPU (MFS) and, optional,


REACHABILITY_ TEST_LABEL_ TEL_GB_GPU (MFS)

REACHABILITY_ TEST_ADDR_ TEL_GSL_GPU (MFS) and, optional,


REACHABILITY_ TEST_LABEL_ TEL_GSL_GPU (MFS)

REACHABILITY_ TEST_ADDR_ TEL_IPGCH_GPU (MFS) and, optional,


REACHABILITY_ TEST_LABEL_ TEL_IPGCH_GPU (MFS)

Set the VLAN_CONF_INDEX parameter to 3.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
3-20
3MN-01075-1873-PGZZA
Issue 6 November 2012

I4P Transport Management


in 9125 TC

Overview
Purpose

This section is dedicated to the IP addressing of the 9125 TC subsystem.


Contents
LAN Configuration

4-1

Reachability Test

4-7

LAN Configuration
Overview

Telecom over IP features are only supported in one LAN topology.


Note: The following convention applies for a 9125 TC equipped with a TC STM1 - IP
subrack:

The TC STM1 interface board is also referred to as TCIF


The TC STM1 IP interface board is also referred to as TCIFI.

...................................................................................................................................................................................................................................
Alcatel-Lucent BSS
4-1
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9125 TC

LAN Configuration

....................................................................................................................................................................................................................................

The necessary parameters for this configuration are set in the TC as shown in the
following table.
Table 4-1

Parameters for LAN Configuration

Parameter Name

Purpose

Values

TCIF1 O&M IP Address

Static IP address of TCIFboard


1 (slot 0) to low layer O&M
access.

A static address that can be


used for specific O&M
operations that are
requested to be done on
TCIF1 board.

TCIF2 O&M IP Address

Static IP address of TCIF board


2 (slot 1) to low layer O&M
access.

A static address that can be


used for specific O&M
operations that are
requested to be done on
TCIF2 board and not on
TC rack as a whole

TCIF Active IP Address

IP address of Active TCIF to


O&M.

IP address used by OMC


and TC-NEM for O&M
control of TCIF.

TCIF1 Telecom IP Address

IP address of TCIF1 (slot 0) to


Telecom access.

IP address of the TCIF1 in


the Telecom subnet used
for reachability purpose.

TCIF2 Telecom IP Address

IP address of TCIF2 (slot 1) to


Telecom access.

IP address of the TCIF2 in


the Telecom subnet used
for reachability purpose.

Note:

The values for TCIF1 Telecom IP Address,


TCIF2 Telecom IP Address and
TCSL Target IP Address must be different.
TCSL Target IP Address

IP address of the TCSL link on


TC side.

Floating TCSL IP address


used by TC to
communicate to 9130
Evolution BSCs.

Note:

If no flow separation is selected, the value for


TCSL Target IP Address must be the same with
TCIF Active IP Address.
TRAUP IP Address

IP address of the TC, used for


IPTCH flow (MUXTRAUP)
and for TC-TC flow (eTRAUP)

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
4-2
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9125 TC

LAN Configuration

....................................................................................................................................................................................................................................

Table 4-1

Parameters for LAN Configuration

(continued)

Parameter Name

Purpose

Values

M2UA TC IP Address SG1

IP address of the TC on the


processor SG1, used for
IP_BSSAsig flow
(M2UA/SCTP signalling
between BSC and TC and
coming from/going to A
interface).

The traffic is between


BSC and TC.

IP address of the TC on the


processor SG2, used for
IP_BSSAsig flow
(M2UA/SCTP signalling
between BSC and TC and
coming from/going to A
interface).

The traffic is between


BSC and TC.

M2UA TC IP Address SG2

Address used on TC by the


two processors Power
Quick3 with signalling
gateway function.

Address used on TC by the


two processors Power
Quick3 with signalling
gateway function

Note:

There is no mandatory rule to set this IP, but it must be


different from M2UA_TC_ IP_Address_SG1 (for example, it
can be incremented).
NTP1 Server Address

Address of NTP server number


1

NTP2 Server Address

Address of NTP server number


2

NTP3 Server Address

Address of NTP server number


3

External OAM Router

IP address to be used by the TC


for testing the access to the
external network for O&M
needs

External OAM Mask

Gives the mask of the subnet


where is allocated the range of
TC addresses used for O&M

To be defined as the size


of the Telecom Subnet :
shall be higher than or
equal to 6 hosts (encoded
in 3 bits). => default
value: 255.255.255.248
for 6 hosts (/29 as prefix
Network)

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
4-3
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9125 TC

LAN Configuration

....................................................................................................................................................................................................................................

Table 4-1

Parameters for LAN Configuration

(continued)

Parameter Name

Purpose

Values

External Telecom Router

IP address to be used by the TC


for testing the access to the
external network for telecom
needs.

External Telecom Mask

Gives the mask of the subnet


where is allocated the range of
TC addresses used for telecom
protocols

To be defined as the size


of the Telecom Subnet:
shall be higher than or
equal to 6 hosts (encoded
in 3 bits). => default
value: 255.255.255.248
for 6 hosts (/29 as prefix
Network)

Internal IP Network Address

IP Address for internal network

Internal IP Network Mask

Gives the mask of the internal


IP network

VLAN Separation

Allows the selection of the


appropriate internal VLAN tags
to use at TC SW level.

Default, checkbox is
unchecked, no flow
segregation.

The following table describes the TC flows and ports to be used.


Table 4-2

TC Flow and Ports

VLAN Separation

TCIF ports
RJ2-x

RJ1-x

Where x is TCIF slot (0, 1)


checkbox is unchecked

O&M + Telecom

O&M + Telecom

checkbox is checked

O&M

Telecom

To change 9125 TC IP address plan, refer to Change IP Address Plan, to 9125 TC IP


addressing plan change.
O&M and Telecom with One Shared Subnet

For both O&M and Telecom transport modes, one external subnet is used, as shown in the
following figure.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
4-4
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9125 TC

LAN Configuration

....................................................................................................................................................................................................................................

Figure 4-1 9125 TC in One LAN Configuration (O&M and Telecom are Mixed)

For CS call-mix traffic (more than 1300E), the forwarding rate of the router can be higher
than 60kpps with 1500-byte packets.
Two Subnets for Separate O&M and Telecom

For separate O&M and Telecom flows, two subnets are used, as shown in the following
figure.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
4-5
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9125 TC

LAN Configuration

....................................................................................................................................................................................................................................

Figure 4-2 Two Subnets for Separate O&M and Telecom

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
4-6
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9125 TC

Reachability Test

....................................................................................................................................................................................................................................

Reachability Test
Overview

The TCIF performs a reachability test:

An ICMP ping request of a O&M address:REACHABILITY_TEST_ADDR_O&M


The default period for O&M is 30 seconds.
An ARP request of a telecom address ( if the telecom feature is activated):REACHABILITY_TEST_ADDRESS_TEL
The default period for telecom is 500 milliseconds.

The active TCIF knows the status of the TCIF1-O&M, TCIF1-TEL, TCIF2-O&M,
TCIF2-TEL, and its decision is to privilege the telecom flow. If no telecom flow is
available, the O&M flows is defended. Also, the standby TCIF performs reachability test
in order to report the link status to the active TCIF.
The following example explains the system behavior.
TCIF1 is active and TCIF1-O&M, TCIF1-TEL, TCIF2-O&M, TCIF2-TEL links are OK:

If the active O&M link fails, a TCIF takeover is triggered and the TCIF2 becomes
active: TCIF1-TEL, TCIF2-O&M, TCIF2-TEL links OK and TCIF1-O&M link NOK

If the telecom flow of TCIF2 fails, a TCIF takeover is triggered and the TCIF1
becomes active: TCIF1-TEL, TCIF2-O&M links OK and TCIF1-O&M, TCIF2-TEL
links NOK
If the telecom flow of the TCIF1 fails, a TCIF takeover is triggered and the TCIF2
becomes active: TCIF2-O&M link OK and TCIF1-TEL, TCIF1 O&M, TCIF2-TEL.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
4-7
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9125 TC

Reachability Test

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
4-8
3MN-01075-1873-PGZZA
Issue 6 November 2012

I5P Transport Management


in 9100 BTS

Overview
Purpose

This section is dedicated to the IP addressing of the 9100 BTS subsystem.


Contents
9100 BTS IP Addressing in IP over E1 (IPoE1) Configuration

5-1

9100 BTS IP Addressing in IP over Ethernet (IPoEth) Configuration

5-4

Security Interface Specifications

5-7

BTS NEM users

5-8

Bidirectional Forwarding Detection (BFD) Protocol

5-11

9100 BTS IP Addressing in IP over E1 (IPoE1) Configuration


Overview

For Telecom transport, it is one external subnet, as shown in the following figure.

...................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-1
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9100 BTS

9100 BTS IP Addressing in IP over E1 (IPoE1) Configuration

....................................................................................................................................................................................................................................

Figure 5-1 BTS IP in IP over E1 (IPoE1) Configuration

The following table shows the necessary parameters for this LAN configuration.
Table 5-1

Parameters for LAN Configuration

Parameter Name

Purpose

Values

IP_Ethernet_Topology

Indicates whether a one LAN or


two Lan solution is used.

One LAN

BSS_Transport_Mode

Indicates whether BSC uses a


TDM or an IP transport on Ater
level.

Telecom transport

BTS_IP_Interface-used

Indicates which BTS IP


interface is used. Directly
deduces by BSC from the Abis
topology.

IP over E1

BTS_IP_Identifier and
BTS_IP_Identifier_Length

Used by BTS and DHCP in


order to determine the IP BTS

String. By default QMUX


address converted in
string.

DHCP_Location

Specifies for an IP BTS if the


DHCP server is located in the
OMC-R or not.

DHCP located in the


OMC-R.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-2
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9100 BTS

9100 BTS IP Addressing in IP over E1 (IPoE1) Configuration

....................................................................................................................................................................................................................................

Table 5-1

Parameters for LAN Configuration

(continued)

Parameter Name

Purpose

Values

DHCP_SERVER_IP_
ADDRESS

Specifies the DHCP server IP


address that is used by TPGSM
for DHCP relay.

The following table shows the parameters for the definition of the subnet E.
Table 5-2

Parameters for Subnet E

Parameter Name

Purpose

Values

IPoE1-IP-Subnet-mask

Gives the mask of the external


subnet.

can be higher than or equal to


16 BTS (>= /28)

Start_IPoE1IP-Address

Starting IP addresses of the


BTS.

First IP address of the subnet E

The subnet E is the external and visible subnet from the IP Telecom network.
The subnet E is defined by its first address Start-IPoE1-IP-Address and the size of this
subnet is given by the IPoE1-IP-Subnet-mask.
The external IP addresses of the BTS are part of the subnet E. Each BTS is assigned n
external IP addresses, where n is the size of the E subnet. The IP address of each BTS is
then computed as follows:
BTS-IP-Address = Start-IPoE1-Address + E1_Link_ID * IPoE1-IP-Subnet-mask

Where E1_Link_ID is the E1 link identifier of the E subnet (between 0 and 251)
To reach the BTS boards of this BSC in the E subnet, the following BTS IP addresses
based on the configuration parameters are set by the OMC at BTS IPoE1 creation and
cannot be modified by the operator. Then the OMC configures the DHCP server
(necessarily local to the OMC for this type of BTS) with the BTS_IP_identifier and the
BTS_IP_Address. Finally, the BTS gets its IP address from DHCP request.
Table 5-3

Address Plan for BTS in IP over E1 (IPoE1) Configuration

Boards

IP Address

BTS A

Start-IPoE1-IP-Address + E1_Link_ID (A) *


IPoE1-IP-Subnet-mask

BTS B

Start-IPoE1-IP-Address + E1_Link_ID (B) *


IPoE1-IP-Subnet-mask

...

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-3
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9100 BTS

9100 BTS IP Addressing in IP over Ethernet (IPoEth)


Configuration

....................................................................................................................................................................................................................................

9100 BTS IP Addressing in IP over Ethernet (IPoEth)


Configuration
Overview

The following table shows the necessary parameters for this LAN configuration.
Table 5-4

Parameters for LAN Configuration

OMC-R Parameter
Name

BTS Parameter
Name

Purpose

Values

Abis transport mode

Transmission Mode

Defines the
transport mode of
an Abis

IP over Ethernet

BTS_IP_Interfaceused

Abis Connected
Interface

Indicates which
physical BTS
interface is used

Ethernet

BTS_IP_Identifier

DHCP client ID

Used by BTS and


DHCP server in
order to determine
the IP BTS address

The value of this


parameter will be set
by operator, except for
the BTS installed in
previous releases case,
when the BTS IP
identifier parameter is
built from QMUX
address at migration
time.

DHCP_Location

Specifies for an IP
BTS if the DHCP
server is located in
the OMC or not
DHCP usage

Usage of DHCP
(external one or
OMC one) or usage
of manually
configured IP
address

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-4
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9100 BTS

9100 BTS IP Addressing in IP over Ethernet (IPoEth)


Configuration

....................................................................................................................................................................................................................................

Table 5-4

Parameters for LAN Configuration

(continued)

OMC-R Parameter
Name

BTS Parameter
Name

Purpose

Values

BTS IP Address

Public IP address

Outer IP address, in
case of IPSEC

Outer IP address, in
case of IPSEC

Defines the BTS IP


address

On the BTS site, the


value of this parameter
will be set by operator
if no usage of DHCP
server. Otherwise, the
BTS gets its IP address
from a DHCP server,
using its BTS IP
identifier.
On the OMC-R site,
the values of this
parameter will be set
by operator, except in
case of usage of DNS,
when the BTS IP
address is resolved
from the BTS
hostname set by
operator.

BTS Hostname

Public IP Subnet
Mask

Defines the mask of


the subnet

Set by operator only if


no usage of DCHP
server. To associate
with parameters Public
IP Address and Default
Gateway IP.

Default Gateway IP

Defines the default


Gateway IP address

Set by operator only if


no usage of DCHP
server. To associate
with parameters Public
IP Address and Public
IP Subnet Mask.

Defines the BTS


hostname
configured in the
DNS

In case of usage of
DNS, OMC-R resolves
the BTS IP address
from the BTS
hostname set by OMC
operator.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-5
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9100 BTS

9100 BTS IP Addressing in IP over Ethernet (IPoEth)


Configuration

....................................................................................................................................................................................................................................

Table 5-4

Parameters for LAN Configuration

OMC-R Parameter
Name
BTS_ROUTING_
SUBGROUP

BTS Parameter
Name

(continued)

Purpose

Values

Only when DHCP


is local to the OMC,
used to configure
the DHCP server.
List of DHCP
parameters : the
Subnet Address, the
IP subnet mask, the
gateway IP address
and the broadcast IP
address.

Subnet address and the


subnet mask define the
subnet in which the
BTS is connected.
Subnet mask is defined
as the size of the
Subnet of the given
BTS. The size of this
subnet shall be higher
than or equal to 16
BTS (encoded in 4
bits).
Gateway IP address
uses to define the IP
addresses of the
Routes towards the
gateway
Broadcast IP address
uses to define the
broadcast IP address to
be used in the BTS
subnet.

To change the BTS IP address plan, refer to Change IP Address Plan, to Change BTS IP
Address Plan.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-6
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9100 BTS

Security Interface Specifications

....................................................................................................................................................................................................................................

Security Interface Specifications


9130 BSC Evolution / BTS SNMP Interface

A fixed SNMP account and password is used.


The account is "BSC_user". For security reasons, the password cannot be given in this
document.
BTS IPsec Interface

The IPsec protocols suite allows building secured tunnels between two entities.
Only ESP Tunnel Mode is supported by the BTS.
On BTS sites, the tunnel termination is embedded in the BTS SUMX board. This board
supports tunnelling to one IPsec gateway only.
The BTS uses a SPD database for static rules definition and an SAD database for
dynamic tunnels management. The BTS operator has to configure the SPD database,
knowing a default configuration is offered by the BTS.
IPSec relies on a first bidirectional tunnel for user authentication and data tunnels control
and two unidirectinal tunnels then established for data exchange.
Strong security negotiation is performed for the bidirectional tunnel by the use of the IKE
asymmetric protocol. Then data are secured in dedicated tunnels by the use of symmetric
key algorithms such as 3DES or AES.
The IPsec authentication of the BTS is performed through IKE/EAP protocol. With IKE
v2, it is possible to use - a standardized way - X.509 certificates stored in a RADIUS
server.
Only IPsec gateways using IKE v2 are supported by the BTS.
The use of certificates is the way to tackle the 'man in the middle' security threat (since a
certificate established by a security authority is needed by the man in the middle).
The IPsec is optional for the operator, depending if the IP network is trusted or not. Hence
an IPsec activation flag is available on the BTS NEM. An IPsec tunnel can only be
activated from the BTS NEM, not from the OMC.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-7
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9100 BTS

BTS NEM users

....................................................................................................................................................................................................................................

BTS NEM users


Overview

There are two possible solutions to provide central management of BTS NEM users:

The use of a Radius server


The use of the OMC for BTS NEM user distribution to the BTS.

Hence it is mandatory that the OMC has to provide a central user management facility
allowing to create through SNMP v3 - BTS NEM users in the BTS. These BTS NEM
users created from the OMC are called pushed users.
This BTS NEM users central management on the OMC impacts the OMC LDAP:

A new attribute for SNMP group is needed


Easier LDAP configuration (web page) is to be provided.

Procedure

When a Radius server is used, the BTS NEM user is authenticated the following way:
...................................................................................................................................................................................................

User enters user name and password, which are different from the default ones.
...................................................................................................................................................................................................

User name and password are sent to the BTS.


...................................................................................................................................................................................................

The BTS (RADIUS NAS client - function) sends an Access Request with User name
and password to the RADIUS server.
...................................................................................................................................................................................................

On reception of the Access Request, the RADIUS server authenticates the user and sent
an Access Accept message to the RADIUS NAS (BTS). The RADIUS server provides
binding between a UserName and a GroupName. The GroupName information is
contained in the filter-ID field of the Access Accept message. The RADIUS server can get
this information from a LDAP server (RADIUS configuration).
...................................................................................................................................................................................................

After successful authentication, User Name, user password and Filter-id are transmitted to
the SNNMP Agent in the BTS in order to create a dynamic USM user.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-8
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9100 BTS

BTS NEM users

....................................................................................................................................................................................................................................
...................................................................................................................................................................................................

SNMPv3 communication is established between SNMPv3 Agent (BTS) and SNMPv3


Manager (PC-NEM).
E...................................................................................................................................................................................................
N D O F S T E P S

BTS Certificates

An X.509 certificate identifies an entity (holds its public key & attributes) is signed by an
authority (with private key), the Certification Authority (CA).
BTS X.509 certificates are used for BTS authentication in the scope of IPsec, EAP-TLS
(within 802.1x for BTS authentication toward a switch) and TLS (for BTS NEM access).
For the BTS certificates signed by the ALU certification authority, a certificate hierarchy
is defined:

An ALU corporate level certificate


An ALU factory level certificate
A BTS level certificate.

The SUM boards are issued from factory with BTS level certificates. On the operator
side, it is possible to configure the different Radius servers used by IPsec gateways or
802.1x authenticators with ALU corporate level certificate only. Such a high level
certificate is enough for validating every BTS certificate instances, thanks to the
certificate's hierarchy (the leaf certificate embeds parent related information, in particular,
their public key used to validate the certificate signature).
In parallel from the ALU certificates (and uppermost), the operator is able to use his own
certificate for the BTS.
TheBTS Certificates can be introduced in the BTS either:

From the factory (for ALU BTS certificate in SUMx case)


From a BTS NEM (for instance in the case of customer certificate at BTS
commissioning time)

From an OMC (for instance for factorization in the case of certificate renewal.

When a BTS certificate is introduced from a BTS NEM or an OMC, several steps are to
be followed (method based on openSSL scenario that relies on corresponding SNMP
attributes):

The BTS comes with a public/private key couple


The NEM/OMC requests a certificate

The BTS returns it unsigned (but with the public key filled)
The unsigned certificate is exported to be off-line signed by the CA

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-9
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9100 BTS

BTS NEM users

....................................................................................................................................................................................................................................

The signed certificate is imported back in the NEM/OMC


The NEM/OMC sends it back to the BTS.

802.1x Port Based Access Control

This IEEE standard, coupled with the EAP protocol, allows Ethernet port protection. The
EAP protocol offers itself several variants. The BTS supports some of them (see more
details at the section end).
802.1x used on a switch provides LAN protection. This standard is very useful in the
context of the BTS access sites that can be easily accessible to unknown users (if not the
BTS itself, probably the LAN access).
We use 802.1x for different protection schemes:

BTS authentication toward the LAN switch

BTS NEM authentication toward the LAN switch (case where the NEM PC is
physically connected to the switch)
BTS NEM authentication toward the BTS (case where the NEM PC is physically
connected to the BTS).

Hence the BTS has to support both the server (toward PC NEM) and client (toward the
LAN switch) 802.1x roles. In 802.1x terminology, the 'server' is called the 'authenticator'
and the client is called the 'supplicant'. The PC NEM only supports the supplicant role.
When authenticator, the BTS uses EAP/PEAP as authentication protocol.
When supplicant, the BTS only supports EAP-TLS as authentication protocol. The
EAP-TLS protocol relies on the use of certificates, which is the means to be used when
the supplicant is a host.
The Radius database for the user holds the user login + password. The Radius database
for the NEM PC holds the PC name + password. The Radius database for the BTS holds
the BTS (or factory) certificate or the BTS name + password if the customer chooses to
not use certificates.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-10
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9100 BTS

Bidirectional Forwarding Detection (BFD) Protocol

....................................................................................................................................................................................................................................

Bidirectional Forwarding Detection (BFD) Protocol


Overview

Bidirectional Forwarding Detection (BFD) is a network protocol used to detect faults


between two endpoints over a particular link. It is a simple 'hello' protocol that in many
respects is similar to the detection components of well-known routing protocols. A pair of
systems transmit BFD packets periodically over each path between the two systems and if
a system stops receiving BFD packets for long enough, some component in that particular
bidirectional path to the neighboring system is assumed to have failed. In this situation,
the BFD can be used as trigger of path switchover between a primary and a secondary
route.
In an IP BSS network architecture, IP Abis traffic is often aggregated from BTS sites in
several points of concentration (POCs) of an access network, before reaching a central IP
gateway, which is the starting point of a secured IP backbone towards TC, BSC, and
MFS. The network access can be a layer 2 or a layer 3 access network. In most of the
cases, it is not owned by the mobile operator, and Abis is backhauled through leased lines
services.
The BFD IP address is used by the "next hop" router which implement the BFD protocol
The address is configured via the BTS terminal and is retrieved by the OMC via through
SNMP
A route is only declared to be operational when two-way communication has been
established between BTS and central IP gateway.
Table 5-5

Parameter for BFD Protocol

Parameter Name

Purpose

Values

BFD_IP_ADDRESS_BTS

Gives the the IP address


used in the BTS for the
BFD protocol.

Default value si 0.0.0.0 and


means BFD is not activated.
In order to be activated, must
be different to 0.0.0.0 and the
BTS_IP_ADDRESS.

To configure the BFD Parameter on CISCO Routers, refer to Reconfigure CISCO Routers
(3BK 17422 4053 RJZZA).

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-11
3MN-01075-1873-PGZZA
Issue 6 November 2012

IP Transport Management in 9100 BTS

Bidirectional Forwarding Detection (BFD) Protocol

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
5-12
3MN-01075-1873-PGZZA
Issue 6 November 2012

BSS Firewall Configuration


6

Overview
Purpose

This section describes the constraints linked to the definition of the ports used by all
protocols.
Contents
Port Handling

6-1

Firewall Positions and Concerned Flows

6-3

Port Handling
Overview
Table 6-1

Flow Port Ranges

Flow

Protocol

Port Range

Parameter Name

TC-TC (eTRAUP)

UDP

52480 - 52526

IPTCH_UDP_
PORT_TC_NONMUX

TCSL

TCP

52528 - 52577

Tcsl-Port-BSCside
(BSC),
Tcsl-Port-BSCside (TC),
Tcsl-Port-TCside (BSC),
Tcsl-Port-TCside (TC)

IP_BSSAsig

SCTP

52592 - 52615

M2UA_SCTP_
PORT_TC,
M2UA_SCTP_
PORT_BSC

...................................................................................................................................................................................................................................
Alcatel-Lucent BSS
6-1
3MN-01075-1873-PGZZA
Issue 6 November 2012

BSS Firewall Configuration

Port Handling

....................................................................................................................................................................................................................................

Table 6-1

Flow Port Ranges

(continued)

Flow

Protocol

Port Range

Parameter Name

IPGSL

TCP

52624 - 52625

IPGSL_BASE_
TCP_MFS,
IPGSL_TCP_
PORT_MFSside (MFS),
IPGSL_TCP_
PORT_MFSside (BSC),
IPGSL_TCP_
PORT_BSCside (MFS),
IPGSL_TCP_
PORT_BSCside (BSC)

Not used

52626 - 52735

OML

UDP

52736 - 52991

BSC-OMLPort-Number,
BTS-OML- Port-Number

RSL

UDP

52992 - 53247

RSL_UDP_PORT_TRX,
RSL_UDP_PORT_BSC

IPGCH-U

UDP

53248 - 53503

IPGCHU_Base_
UDP_MFS,
IPGCHU_UDP_
PORT_MFS,
IPGCHU_UDP_
PORT_BTS

IPGCH-C

TCP

53504 - 54527

IPGCHC_TCP_
PORT_BTS

IPTCH (MUXTRAUP)

UDP

54528 - 54575

IPTCH_UDP_
PORT_TC_MUX,
IPTCH_UDP_
PORT_BTS

Not used

54576 - 54783

Not used

57344 - 61439

This port range is used


for internal IPGCH-C
cross traffic.

54784 - 55039

BDP-Command
-Port-Number,
BDP-Data- Port-Number

BDP

BDP

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
6-2
3MN-01075-1873-PGZZA
Issue 6 November 2012

BSS Firewall Configuration

Port Handling

....................................................................................................................................................................................................................................

Table 6-1

Flow Port Ranges

(continued)

Flow

Protocol

Port Range

Parameter Name

AsigoIP

SCTP

0 - 65535

ASIG_SCTP_
ENDPOINT_PORT
Refer to 'BSS
Configuration Handbook'
3BK 21601 AAAA
PCZZA section Create A
Signalling Link"

Firewall Positions and Concerned Flows


Overview
Figure 6-1 Standard Case

Firewall port ranges to configure in this case is 52736 - 55039.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
6-3
3MN-01075-1873-PGZZA
Issue 6 November 2012

BSS Firewall Configuration

Firewall Positions and Concerned Flows

....................................................................................................................................................................................................................................

Figure 6-2 BSC in Access Network and Central Office

Firewall port ranges to configure in this case is 52528 - 55039.


Figure 6-3 MSC in Access Network and Central Office

Firewall port ranges to configure in this case is 52624 - 55039.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
6-4
3MN-01075-1873-PGZZA
Issue 6 November 2012

DHCP Server
7

Overview
Purpose

This section is dedicated to the DHCP Server configuration.


Contents
DHCP Server Located on 9153 OMC-R

7-1

DHCP Server Located External to 9153 OMC-R

7-2

Without a DHCP Server

7-3

DHCP Relay

7-3

DHCP Server Located on 9153 OMC-R


Overview

If DHCP server located in the OMC-R, the OMC-R configures the DHCP server with the
BTS_IP_identifier and the BTS_IP_address. Then the BTS gets its IP address from the
DHCP request.
The BTS-Routing-SubGroup (and Second-BTS-ROuting-SubGroup) contain the
following parameters:

subnet address

subnet mask
gateway address (optional)
broadcast address (optional)

This group of parameters is valid only in IP over Ethernet transport mode. It is used by
OMC-R to configure the local DHCP server.
The subnet address and the subnet mask define the subnet in which the BTS is connected.
...................................................................................................................................................................................................................................
Alcatel-Lucent BSS
7-1
3MN-01075-1873-PGZZA
Issue 6 November 2012

DHCP Server

DHCP Server Located on 9153 OMC-R

....................................................................................................................................................................................................................................

The gateway address defines the IP address of the gateway to be used by the BTS to route
the IP traffic.
The broadcast address defines the broadcast IP address to be used in the BTS subnet. This
address is not used by the BTS.
This group of parameters is changeable at OMC-R. The local DHCP server is configured
immediately without any telecom traffic impact. The BTS is informed about the change
after the BTS reset. If the gateway address is changed, the new gateway must be
operational before the BTS reset.
When the DHCP Server is located on the OMC-R, the usage of a DNS server is not
necessary. Therefore, the only way to map IP addresses on DHCP server is static.
The value of the DHCP-location parameter is 0, that specifies for an IP BTS that the
DHCP server is located in the OMC-R.
If the DHCP server becomes not available, the BTS uses the last assigned IP address. This
is also applicable for the case when the DHCP Server Located External to 9153
OMC-R (p. 7-2)

DHCP Server Located External to 9153 OMC-R


Overview

In the case of usage of a DNS, the OMC-R configures the DHCP server with the
BTS_hostname and the BTS_IP_identifier. Then the BTS gets its IP address from DNS
request. No BTS IP address is configured in the OMC-R.
The external DHCP server is configured manually. The BTS is informed about the change
after the reset of the BTS.
The usage of a DNS server is available only with an external DCHP server.
The BTS-Hostname parameter is used only if the DNS server is known by the OMC-R. It
is used by the OMC-R to get BTS IP address. Therfore, the BTS-Hostname parameter
must be unique per DNS server.
If the BTS IP address is changed, the traffic towards the BTS is stopped until the BTS
gets its new IP address from the DHCP server.
The value of the DHCP-location parameter is 1, that specifies for an IP BTS that the
DHCP server is located external to the OMC-R.
If the DHCP server becomes not available, the BTS uses the last assigned IP address.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
7-2
3MN-01075-1873-PGZZA
Issue 6 November 2012

DHCP Server

Without a DHCP Server

....................................................................................................................................................................................................................................

Without a DHCP Server


Overview

The operator configures directly the BTS_IP_address as well as the BTS IP Identifier.
Then the BTS gets its IP address from the OMC-R.
The value of the DHCP-location parameter is 1, which specifies that for an IP BTS there
is no DHCP server.

DHCP Relay
Overview

If the BTS network is other than the DHCP server's network, then the DHCP relay must
be configured on the router that connects directly to the BTS network.
The DHCP relay feature relays a request from a remote client to a DHCP server for an IP
address. When the router receives a DHCP request from an IP client, it forwards the
request to the DHCP server and passes the response back to the IP client.
In order to configure DHCP relay, refer to the following documents:

Configure OS6850 for GB/BSS Traffic (3BK 17430 3295 RJZZA)

Reconfigure CISCO Routers (3BK 17422 4053 RJZZA)

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
7-3
3MN-01075-1873-PGZZA
Issue 6 November 2012

DHCP Server

DHCP Relay

....................................................................................................................................................................................................................................

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
7-4
3MN-01075-1873-PGZZA
Issue 6 November 2012

S8TM1 on 9130 BSC


Evolution and 9125 TC

Overview
Purpose

This section is dedicated to the STM1 configuration.


Contents
Introduction

8-1

Introduction
Overview

From Release B11, Alcatel-Lucent provides an alternative solution to TDM transport, the
Synchronous Transport Mode level 1(STM1) in the Synchronous Digital Hierarchy
(SDH) network.
STM1 permits the transportation of larger amounts of telephone calls and data traffic over
the same fiber wire without synchronization problems, using lasers or light-emitting
diodes (LED).

...................................................................................................................................................................................................................................
Alcatel-Lucent BSS
8-1
3MN-01075-1873-PGZZA
Issue 6 November 2012

STM1 on 9130 BSC Evolution and 9125 TC

Introduction

....................................................................................................................................................................................................................................

Figure 8-1 SDH Ring Configuration

The basic unit of framing in SDH is the Synchronous Transport Module level 1 (STM1),
which operates at 155.52 Mbit/s, and which is used in GSM for transporting E1 links.
The STM1 is supported on 9130 BSC Evolution equipped with TPGSM3 boards and on
9125 TC equipped with TCIF boards.
Each E1 link is transported transparently (using asynchronous mapping) in one VC12
container. One STM1 link can contain up to 63 VC12 containers. Therefore, one STM1
can carry 63 E1 links ( Abis / Ater Mux / A), and each E1 of 2048 kbit/s is transported
separately in one VC12 container. With four STM1 interfaces per Network Element (BSC
/ TC), the maximum configuration can be achieved and 252 E1 links can be transported
separately in 252 VC12 containers.
Each STM1 link coming from BSC/TC is connected to an ADM (Add Drop Multiplexer)
and where this ADM equipment is located depends of the operator SDH network.
ADM
....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
8-2
3MN-01075-1873-PGZZA
Issue 6 November 2012

STM1 on 9130 BSC Evolution and 9125 TC

Introduction

....................................................................................................................................................................................................................................

ADM is a device installed at an intermediate point on a transmission line that enables new
signals to come in and existing signals to go out. In a typical example, most signals pass
through the device, but some would be dropped by splitting them from the line. Signals
originating at that point can be added into the line and directed to another destination.
Add/drop multiplexing can be done with optical or electronic signals. The device may
deal only with wavelengths, or it may convert between wavelengths and electronic TDM
signals. The setup in an add/drop multiplexer is generally static and it is in charge of SDH
network administrator.
Figure 8-2 ADM Functional Description

There are multiple manufacturers of ADM, but Alcatel-Lucent recommends the following
(depending of the complexity of the SDH network ):

Alcatel 1642 Edge Multiplexer


Compact, flexible, data-oriented, future-proof, the Alcatel 1642 Edge Multiplexer is
based on 2 x STM-1 line interfaces, 6 x 6 full non-blocking Low-Order SDH matrix,
clock reference and equipment control functions, all concentrated in a 1 slot wide
compact ADM card.
Alcatel 1662 SMC

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
8-3
3MN-01075-1873-PGZZA
Issue 6 November 2012

STM1 on 9130 BSC Evolution and 9125 TC

Introduction

....................................................................................................................................................................................................................................

Scalable, space saving, next-generation multiservice building block for local and
metropolitan networks, providing unmatched performances for its room occupation
and transport mix capabilities, the Alcatel 1662 SMC is based on 2 x STM-1/4 or
1xSTM-16 line interfaces, 32 x 32 or 64 x 64 full non-blocking high order/low order
SDH matrix, clock reference and equipment control functions, all concentrated in a 1
slot wide compact ADM card, optionally 1+1 protected.

....................................................................................................................................................................................................................................
Alcatel-Lucent BSS
8-4
3MN-01075-1873-PGZZA
Issue 6 November 2012

You might also like