bss telecom routing 174385004e28.pdf

8/11/2019 BSS Telecom Routing 174385004e28.pdf

1/100

Alcatel-Lucent GSM

BSS Telecom RoutingConfiguration

BSS Document

Reference Guide

3BK 17438 5004 PGZZA Ed.28


2/100

Status RELEASED

Short title BSS Telecom Routing Configuration

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel-Lucent.

BLANK PAGE BREAK

2 / 100 3BK 17438 5004 PGZZA Ed.28


3/100

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.1 Required Hardware Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2 BSS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.2.1 IPoEth BSS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.2 Mixed Mode BSS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.3 Layer 2 BSS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.4 Layer 3 BSS Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

1.3 IP Telecom Networks Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.4 BSS Communication Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.5 LAN Configuration and Subnets Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.6 General Rules on IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.7 IP TimeToLive Values for BSS over IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2 Management of IP Transport in 9130 BSC Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.1 IP Addressing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.2 O&M and Telecom with One Shared Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.3 Several Subnets for Separate O&M and Telecom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.4 Reachability Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3 Management of IP Transport in 9130 MFS Evolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.1 LAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.2 IP Addressing Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.3 Several Subnets for Separate O&M and Telecom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.4 Reachability Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3.4.1 O&M Reachability Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.4.2 Telecom Reachability Test by the Control Station . . . . . . . . . . . . . . . . . . . . . . . . . . 583.4.3 Telecom Reachability Test by GPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

3.4.4 Reachability Test Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614 Management of IP Transport in 9135 MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

4.1 LAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664.2 Both the O&M and the Telecom flows in IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5 Management of IP Transport in 9125 TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

5.1 LAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725.1.1 O&M and Telecom with One Shared Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.1.2 Two Subnets for Separate O&M and Telecom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.2 Reachability Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

6 Management of IP Transport in 9100 BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6.1 9100 BTS IP Addressing in IP over E1(IPoE1) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

6.2 9100 BTS IP Addressing in IP over Ethernet (IPoEth) Configuration . . . . . . . . . . . . . . . . . . . . 826.3 Security Interfaces Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.3.1 9130 BSC Evolution / BTS SNMP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.3.2 BTS IPsec Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836.3.3 BTS NEM Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846.3.4 BTS Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856.3.5 802.1x Port Based Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

6.4 Bidirectional Forwarding Detection (BFD) Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

7 BSS Firewall Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

7.1 Port Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907.2 Firewall Positions and Concerned Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

8 DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

8.1 DHCP Server Located on 9153 OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

3BK 17438 5004 PGZZA Ed.28 3 / 100


4/100

Contents

8.2 DHCP Server Located External to 9153 OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948.3 Without a DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 958.4 DHCP Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

9 STM1 on 9130 BSC Evolution and 9125 TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

4 / 100 3BK 17438 5004 PGZZA Ed.28


5/100

Preface

Preface

Purpose This document describes the generic BSS Telecom Routing Configurationapplicable for all hardware in the BSS.

Document Pertinence This document applies to Release B11 of the BSS.

This document contains IP transport in the BSS related information. Thisfeature is available commercially from Release B12.

Whats New In Edition 28

SectionO&M Reachability Test (Section 3.4.1) was updated.

In Edition 27Updated the sectionSeveral Subnets for Separate O&M and Telecom (Section3.3)in order to use the VRRP protocol instead of the HSRP protocol.

In Edition 26

Management of IP Transport in 9135 MFSwas added.

In Edition 25The following sections were updated:

Management of IP Transport in 9130 BSC Evolution (Section 2)

Management of IP Transport in 9130 MFS Evolution (Section 3)Added section9100 BTS IP Addressing in IP over E1(IPoE1) Configuration(Section 6.1)

In Edition 24

Several Subnets for Separate O&M and Telecom (Section 2.3) was updated.


O&M and Telecom with One Shared Subnet (Section 2.2)

Several Subnets for Separate O&M and Telecom (Section 2.3)

3BK 17438 5004 PGZZA Ed.28 5 / 100


6/100

Preface

In Edition 22

SectionO&M and Telecom with One Shared Subnet (Section 2.2) was updatedfollowing the introduction of the BSC Evolution with 1400 TRX feature forRelease B12.

In Edition 21Overall document quality was improved following an editorial review.

6 / 100 3BK 17438 5004 PGZZA Ed.28


7/100

Preface

In Edition 20The following sections were updated following the introduction of the AUP overIP feature for Release B12:


Several Subnets for Separate O&M and Telecom (Section 2.3).

In Edition 19

Port Handling (Section 7.1)was updated.

In Edition 18

LAN Configuration (Section 5.1) was updated.

In Edition 17


In Edition 16Document Pertinencewas updated to specify that IP transport in the BSS isavailable from Release B12.

Bidirectional Forwarding Detection (BFD) Protocol (Section 6.4) was updated.

In Edition 15


IP TimeToLive Values for BSS over IP (Section 1.7) was added.

In Edition 14

First official release of the document.

Release name was changed inDocument pertinence.The following sections were updated:



Reachability Test (Section 2.4)


Reachability Test (Section 3.4)

No Flow Separation(Section 3.4.4.1)

O&M and Telecom Flows Separation(Section 3.4.4.2)

O&M, Gb and BSS Flows Separation(Section 3.4.4.3)

Full Flows Separation(Section 3.4.4.4)

LAN Configuration (Section 5.1)

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

6.2)

802.1x Port Based Access Control (Section 6.3.5).

The following new sections were added:

3BK 17438 5004 PGZZA Ed.28 7 / 100


8/100

Preface

BSS Communication Plan (Section 1.4)

LAN Configuration and Subnets Summary (Section 1.5).

In Edition 13

The release name was changed in Document pertinence.

In Edition 12

O&M and Telecom Flows Separation(Section 3.4.4.2)was updated.

In Edition 11

9100 BTS IP Addressing in IP over Ethernet (IPoEth) Configuration (Section6.2) was updated.

In Edition 10








Reachability Test (Section 3.4).

In Edition 07


In Edition 06

Several Subnets for Separate O&M and Telecom (Section 3.3) was updated

In Edition 05

LAN Configuration (Section 5.1) was updated




In Edition 03

Reachability Test (Section 3.4) wasupdated with information concerning thereachability tests.

8 / 100 3BK 17438 5004 PGZZA Ed.28


9/100

Preface

In Edition 02

The ASIG_PRIORITY parameter was added in the The telecom parametersfor LAN configuration table.

In Edition 01

First official release of the document.

3BK 17438 5004 PGZZA Ed.28 9 / 100


10/100

Preface

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.

Assumed Knowledge You must have a basic understanding of Alcatel-Lucent BSS equipment andIP routing

10 / 100 3BK 17438 5004 PGZZA Ed.28


11/100

1 Overview

1 Overview

This Overview provides background information about the generic BSSTelecom Routing Configuration and its environment.

3BK 17438 5004 PGZZA Ed.28 11 / 100


12/100

1 Overview

1.1 Required Hardware Elements

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.

Required Layer 3 Routing Protocols (IPv4):

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

IP Routing: OSPF v2

Redundancy: VRRP v2.

12 / 100 3BK 17438 5004 PGZZA Ed.28


13/100

1 Overview

1.2 BSS Architecture

1.2.1 IPoEth BSS Architecture

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

The 9130 BSC, TC, and 9130 MFS are connected through the IP networkof the operator.

The CS user plane is passed directly to the TC over IP, while the CS controlplane is directed towards the BSC.

This is shown in the following figure.

OMCR

QA, QB

A

MSC

MFS

SGSN

Gb

IP backbone

IPoEthernetBTS

MxBSC

TC

BTS

BTS

Figure 1: Full IPoEth BSS

1.2.2 Mixed Mode BSS Architecture

This mode allows the BSS to simultaneously handle some BTS in TDM mode

(for example, B10) and others in IP mode (IPoEth).It allows the operator to progressively introdcue IP into the network.

1.2.3 Layer 2 BSS Architecture

Using a Layer 2 transport network means that, despite the BSS NEs (BTS,BSC, TC, MFS) will still exchange IP packets, the underlying functionalarchitecture of the transport network can be seen as a single LAN, in practicean Ethernet LAN. Taking into account the potential distance betweennetwork elements, this will be based on "Extended Area LAN" concepts likeMetroEthernet ones. The primary impact on the IP-based transport is then thatall 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, thisIP router can be added (anywhere) on top of an Ethernet network, like in theexample highlighted in the figure below.

3BK 17438 5004 PGZZA Ed.28 13 / 100


14/100

1 Overview

CoreEthernetSwitch

EthernetSwitch 1

EthernetSwitch 2

EthernetSwitch

EthernetSwitch

EthernetSwitch 3

EthernetSwitch 4

BTS

BTSBTSBTSBTS

BTS BSCBSC

TC

MFS

RouterOperatorL2 Network

VLAN1

VLAN1, VLAN2, VLAN3

VLAN1,VLAN2, VLAN3

VLAN3VLAN2

CentralSite

BTSSite1

BTSSite3

BTSSite2

E1 E1

Ethernet switches 1, 2, 3, 4 are access points to the operators network.

The core ethernet switch represents the interconnections inside the operatorsnetwork.

VLAN tags 1, 2, 3 represent traffic from / to Ethernet LANs 1, 2, 3. They canbe configured on the ethernet switches 1, 2, 3, 4, the core network nodes,and the router.

Since there are 3 different VLANs, there are also 3 different IP subnets, and theRouter must be assigned one IP address in each of these subnets.

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 2 are only needed ifthe operator wants to (or must) manage different subnets for BTS in LANs 1and 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 usedfor LAN 1 and 2. VLAN 3 is only needed if BSC is not in this subnet, as well asVLAN 4 for the Central Office controllers.

No route needs to be configured on the IP router, since only its local interfacesare involved in the used routes

1.2.4 Layer 3 BSS Architecture

The Layer 3 Alcatel-Lucent OmniSwitch 6850 is used as an example forconfiguring the BSS layer 3 architecture.

For more information about OmniSwitch 6850, refer toConfigure OS6850 forGB/BSS Traffic(3BK 17430 3295 RJZZA).

1.2.4.1 Controllers in Different NetworksMFS, BTS, TC are in different sub networks. In this case, each machine definesits proper subnet, as shows in the following figure.

14 / 100 3BK 17438 5004 PGZZA Ed.28


15/100

1 Overview

Ethernet

BTS BTS

E1

BTS

L3 Managed SW1 L3 Managed SW2Central Router

Vlan Bss 1

Vlan Bss 2

Vlan Bss n1

Vlan Bss n

To Bss 1

To Bss 2

To Bss n1

To Bss n

Vlan B

@Vrrp id 3

@Vrrp id 2

@Vrrp id 1

ip fl@TC

ip fl@MFS

ip fl@BSC

BSC MFS TC

Vlan A1

Vlan A2

Vlan A3

Vlan A1

Vlan A2

Vlan A3

Vlan B

L3 Managed SW

Vlan C

Figure 2: Different LAN BSS Architecture

3BK 17438 5004 PGZZA Ed.28 15 / 100


16/100

1 Overview

1.2.4.2 All Controllers in Same Network

The MFS, BTS, and TC are in the same subnetwork, as shown in the figurebelow.

A common subnet allows:

Simplification of the IP management (only one subnet to manage)

Saving IP ports on the routers (L3 ports on routers are more expensive

than L2 ports).

Vlan A

Ethernet

BTS

E1

BTS

L3 Managed SW1 L3 Managed SW2

Vlan A

Vlan B Vlan B

@Vrrp id 1

@Vrrp id 2

Central Router

Vlan Bss 1

Vlan Bss 2

Vlan Bss n1

Vlan Bss n

To Bss 1

To Bss 2

To Bss n1

To Bss n

BSC MFS TC

L3 Managed SW

BTS

Figure 3: One LAN BSS Architecture

16 / 100 3BK 17438 5004 PGZZA Ed.28


17/100

1 Overview

1.3 IP Telecom Networks Overview

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

9130 BSCEvolution

IP

IP

IPIP

IP

IP

IP IP

Evolution

TC

BTS

IP Telecom Network

DHCPServer

MSC

SGSN

NEM

Figure 4: IP Telecom Networks

1.4 BSS Communication Plan

The following table represents the communication plan.

9130BSCEvolution

9130MFSEvolution

9135MFS

9125 TC 9100BTS

9153

OMC-R

MSC SGSN

9130

BSC

Evolution

Notapplicable

Telecom Notapplicable

Telecom Telecom O&M Telecom Telecom

9130

MFS

Evolution


Notapplicable

Notapplicable

Telecom O&M Telecom Telecom

9135

MFS

Notapplicable

Notapplicable

Notapplicable

Notapplicable

Notapplicable

O&M Telecom Telecom

9125 TC Telecom Notapplicable

Notapplicable

Telecom Telecom O&M Telecom Notapplicable

9100

BTS


Notapplicable

Telecom Telecom O&M Notapplicable

Notapplicable

9153

OMC-R

O&M O&M O&M O&M O&M O&M Notapplicable

Notapplicable

3BK 17438 5004 PGZZA Ed.28 17 / 100


18/100

1 Overview

9130BSCEvolution

9130MFSEvolution

9135MFS

9125 TC 9100BTS

9153

OMC-R

MSC SGSN

TC NEM Not

applicable

Not

applicable

Not

applicable

O&M Not

applicable

Not

applicable

Not

applicable

Not

applicable

9130

BSC

Evolution

NEM

O&M Notapplicable

Notapplicable

Notapplicable

Notapplicable

Notapplicable

Notapplicable

Notapplicable

9135

MFS /

9130

MFS

Evolution

IMT

Notapplicable

O&M O&M Notapplicable

Notapplicable

Notapplicable

Notapplicable

Notapplicable

BTS

NEM

Notapplicable

Notapplicable

Notapplicable

Notapplicable

O&M Notapplicable

Notapplicable

Notapplicable

Table 1: O&M / Telecom Flow Segregation Table

The MFS IMT, BTS NEM, BSC NEM, and TC NEM dialogue with correspondingNEs in the O&M communication plan. NEM remotely connected to an NE areusually located in an O&M site. To have a NEM connected from a telecom site,it is necessary that the O&M addresses are routable up to this site.

The MSC and SGSN are not BSS NEs but core network NEs with interfaces to

the BSS.

18 / 100 3BK 17438 5004 PGZZA Ed.28


19/100

1 Overview

1.5 LAN Configuration and Subnets Summary

The following table summarizes the different LAN configurations and therelated subnets.

LAN Topology IP Transport ModePossibility

ExternalSubnet(s)

Network ElementImpacted

Comments

O&M only A 9130 MFS

Evolution

9135 MFS

9130 BSC

Evolution

9125 TC

A is the only oneexternal subnetdedicated to O&M

O&M and Telecomwith one sharedsubnet

A 9130 MFS

Evolution

9130 BSC

Evolution

9125 TC

A is the externalSubnet shared byO&M and Telecom

O&M and Telecomwith two seperatesubnets

A1, A2 9130 MFS

Evolution

9135 MFS

9130 BSCEvolution

9125 TC

A2 is the externalsubnet withTelecom whenA1 is dedicated toO&M

One LAN

O&M and Telecomwith separatesubnets and withseveral telecomsubnets

A1, A2, A3, A4, A5 9130 MFS

Evolution

9130 BSC

Evolution

A2, A3, A4 are theexternal subnetswith Telecom whenA1 is dedicated toO&M

Two LAN O&M only A 9130 MFS

Evolution9130 BSC

Evolution

A is the externalsubnet and there

are 2 local subnetsnamed B and C

Table 2: Summarize LAN Configuration and Subnets

3BK 17438 5004 PGZZA Ed.28 19 / 100


20/100

1 Overview

1.6 General Rules on IP Addressing

The operator must be able to group the IP addresses according to his ownorganization.

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 subnetshandled by the external routers, which allows using lower cost routers. Thisrequirement is especially interesting when several 9130 BSC Evolution areco-localized or when the 9130 BSC Evolution is co-localized with the 9130MFS Evolution.

The operator must be able to separate the O&M IP addresses from the TelecomIP addresses in two different subnets.

The first and the last IP addresses in a subnet are reserved, respectively toidentify the subnet addresses and the broadcast address. They must beremoved from the list of IP addresses that can be assigned to the hosts. Forinstance, 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.

The external router is part of the customer network and it is up to the customerto configure it with IP addresses.

20 / 100 3BK 17438 5004 PGZZA Ed.28


21/100


22/100

1 Overview

22 / 100 3BK 17438 5004 PGZZA Ed.28


23/100

2 Management of IP Transport in 9130 BSC Evolution


This section is dedicated to the IP addressing of the 9130 BSC Evolutionsubsystem only.

3BK 17438 5004 PGZZA Ed.28 23 / 100


24/100


2.1 IP Addressing Rules

IP addresses for a 9130 BSC Evolution can be chosen freely, limited only bythe 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..65, 192.168..66 where means Shelf

Geographical Address and can have the value 3 or 4.

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

172.16/16, 172.17/16, 172.18/16


Geographical Address and can have the value 3 or 4

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.

2.2 O&M and Telecom with One Shared Subnet

The AUPoIP (A User Plane Over IP) is available commercially with the ReleaseB12.

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

9130 BSC Evolution

AlarmBox SSW1

OMCP2

OMCP1

Route B

Route C

port 3

port 3

Router 1

Router 2

VRRP

SSW2

TPGSM

OCPx

IP O&M / TelecomNetwork

Subnet A

Figure 5: 9130 BSC Evolution in One LAN Configuration with VRRP (O&M andTelecom are Mixed)

24 / 100 3BK 17438 5004 PGZZA Ed.28


25/100


26/100


Parameter name Purpose Values

EN_ASIG_OVER_IP Indicates whether the9130 BSC Evolutionuses an TDM or an IP Asignalling

True

EN_AUP_OVER_IP Indicates whether the9130 BSC Evolutionuses a TDM, a mixedTDM - IP mode or an IPA User Plane.

True

IP_EXTLINK_SHARING

Indicates if the O&M linkis shared with a 9130

MFS Evolution or not.

No

BSC_IP_O&M_SUBNET_ MASK

Gives the mask of theexternal subnet A forO&M

Shall be higher than orequal to 32 hosts (/27minimum).

START_O&M_IP_ADDRESSES

Indicates the first IPaddress of the rangereserved for the BSC inSubnet A for O&M

START_ASIG_IP_

ADDRESS_ BSC

Start address for the

A Signalling over IP(ASigoIP) subnet. Therange size is 2

No default value.

Shall be equal toStart_O&M_IP_Address+ 2

ASIG_IP_SUBNET_MASK_BSC

Subnet mask for theA Signalling over IP(ASigoIP) subnet.

The minimumrange size is 2.Shall be equal toBSC_IP_O&M_Subnet_Mask

START_BSS_IP_ADDRESS_BSC

Start address for theBSS over IP (BSSoIP)subnet. The range sizeis 10.

No default value.Shall be equal toStart_O&M_IP_Address+ 2

BSS_IP_SUBNET_MASK_BSC

Subnet mask for theBSS over IP (BSSoIP)subnet

The range size is 10.Shall be equal toBSC_IP_O&M_Subnet_Mask

26 / 100 3BK 17438 5004 PGZZA Ed.28


27/100



START_AUP_IP_ADDRESS_BSC

Start addres for theA User Plane overIP (AUPoIP) addressrange.

No default value.Shall be equal toStart_O&M_IP_Address+ 2.

AUP_IP_SUBNET_MASK_BSC

Subnet mask for thesubnet where A UserPlane over IP (AUPoIP)

addreses are located.

The minimumrange size is 3.Shall be egual to

BSC_IP_O&M_Subnet_Mask

START_ADD_FUNC_IP_ADDRESS_BSC

Start address for the Lband/or Iur-g IP addressrange

No default value.Shall be equal toStart_O&M_IP_Address+ 2

ADD_FUNC_IP_

SUBNET_MASK_BSC

Subnet mask for the

subnet where Lb and/orIur-g IP addresses arelocated

The minimum

range size is 2.Shall be equal toBSC_IP_O&M_Subnet_Mask

VLAN_CONF_INDEX Allows the selection ofthe appropriate internalVLAN tags to use atBSC switch level

common tagging

ROUTING_TABLE(BSC)

Defines the list of staticroutes. Each route isdefined by :

the destination IPaddress

the destination IP

subnet mask

the gateway IP

address

To define the IPaddresses of the Routestowards the gateway(used by the BSC for

sending IP packets tothe external world)

Table 4: Telecom Parameters for Subnet A Definition

3BK 17438 5004 PGZZA Ed.28 27 / 100


28/100


For the reachability test, the necessary telecom parameters are set in the9130 BSC Evolution, as shown below:


REACHABILITY_TEST_ADDR_O&M

IP address to be used bythe BSC for testing theaccess to the externalnetwork for O&M needs

Address of the gateway

REACHABILITY_TEST_ADDR_ASIG

IP Address to beused by the BSC fortesting the access tothe external networkfor A Signalling over

IP (ASigoIP) Telecomneeds.

Address of thegateway used for ASignalling over IP(ASigoIP) Telecomneeds. Same value as


REACHABILITY_TEST_ADDR_BSS

IP Address to be usedby the BSC for testingthe access to theexternal network forBSS over IP (BSSoIP)telecom needs

Address of the gatewayused for BSS over IP(BSSoIP) Telecomneeds. Same value asREACHABILITY_TEST_ADDR_O&M

REACHABILITY_TEST_ADDR_ADD_FUNC

IP Address to be usedby the BSC for testingthe access to the

external network forLb and/or Iur-g over IPTelecom needs

Address of the gatewayused for Lb and/orIur-g over IP Telecom

needs. Same valueas REACHABILITY_TEST_ADDR_O&M

REACHABILITY_TEST_ADDR_ AUP

IP Address to beused by the BSC fortesting the access tothe external networkfor A User Plane overIP (AUPoIP) telecomneeds.

Address of thegateway used for AUser Plane over IP(AUPoIP) Telecomneeds. Same valueas REACHABILITY_TEST_ADDR_O&M

Table 5: Telecom Parameters for Reachability Test

To reach the BSC OMCP boards, the Alarm box and the CCP boards fromeverywhere in the IP O&M network, the external IP addresses based on theSTART_O&M_IP_ADDRESS are set in the 9130 BSC Evolution as shownbelow:

Boards IP Address

9130 BSC Evolution OMCP1 Start_O&M_IP_Address

9130 BSC Evolution OMCP2 Start_O&M_IP_Address + 1

28 / 100 3BK 17438 5004 PGZZA Ed.28


29/100


Boards IP Address

9130 BSC Evolution active OMCP Start_O&M_IP_Address + 2

9130 BSC Evolution active OMCP

standby plane (for O&M standbyplane 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


Table 6: External IP addresses for O&M

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 externalIP addresses based on the START_ASIG_IP_ADDRESS_BSC are set in the9130 BSC Evolution as shown below:

Boards IP Address

9130 BSC Evolution active OMCP Start_Asig_IP_Address_BSC

9130 BSC Evolution active OMCPstandby plane (for Telecom standbyplane reachability test)

Start_Asig_IP_Address_BSC + 1

Table 7: External IP addresses for A Signalling over IP (AsigoIP)

For A User Plane over IP (AUPoIP), to reach the BSC OMCP boards and theTPGSM from everywhere in the IP network, the external IP addresses basedon the START_AUP_IP_ADDRESS_BSC, are set in the 9130 BSC Evolution asshown below:

Boards IP Address BSC Parameter Description

9130 BSCEvolution active

OMCP

START_AUP_IP_Address

_BSC

3BK 17438 5004 PGZZA Ed.28 29 / 100


30/100



9130 BSCEvolutionactive OMCP

standby plane(for Telecomstandby planereachabilitytest)

START_AUP_IP_Address_BSC + 1

9130 BSCEvolution activeTPGSM/TPIP


RTP_IP_ADDRESS_ BSC

RTP_IP_ Addressaddresses of theRTP and MUXRTPTPIP data pathtermination. TheRTP function issupported by the

TPIP (TPGSM).

Table 8: External IP addresses for A User Plane over IP (AUPoIP)

For BSS over IP (BSSoIP), to reach the BSC OMCP boards, the TPGSM andhe CCP boards, from everywhere in the IP Telecom network, the external IPaddresses based on the Start_BSS_IP_Address_BSC, are set in the BSC, asshown below:

Boards IP Address

9130 BSC Evolution active OMCP Start_BSS_IP_Address_BSC

9130 BSC Evolution active OMCPstandby plane (for standby planereachability 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





30 / 100 3BK 17438 5004 PGZZA Ed.28


31/100


Boards IP Address



Table 9: External IP addresses for BSS over IP (BSSoIP)

For LB / Iur-g over IP, to reach the BSC OMCP boards, the Alarm box, the CCPboards from everywhere in the IP Telecom network, the external IP addressesbased on the Start_Add_Func_IP_Address_BSC are set in the 9130 BSCEvolution, as shown below.

Boards IP Address

9130 BSC Evolution active OMCP Start_Add_Func_IP_Address_BSC


Start_Add_Func_IP_Address_BSC+ 1

Table 10: External IP addresses for Lb / Iur-g over IP

To change 9130 BSC Evolution IP address plan, use Change IP Address Plan,in the case of Common O&M and Telecom flows in BSC.

3BK 17438 5004 PGZZA Ed.28 31 / 100


32/100


2.3 Several Subnets for Separate O&M and Telecom

The A User Plane over IP (AUPoIP) feature is available commercially withthe B12 release.

For O&M and Telecom transport mode, the following subnets are used, asshown in the figures below:

A1 - O&M subnet

A2 - AsigoIP subnet

A3 - BSSoIP subnet

A4 - Lb / Iur-g subnet

A5 - AUPoIP subnet

32 / 100 3BK 17438 5004 PGZZA Ed.28


33/100


9130 BSC Evolution

AlarmBox

Router 2P

Router 2S

VRRP

AsigoIPNetwork

Subnet A1 for O&M Router 1P

Router 1S

IP O&M Network

VRRP

Subnet A2 for AsigoIP

Router 3P

Router 3S

BSSoIP

NetworkVRRP

Subnet A3 for BSSoIP

Router 4P

Router 4S

Lb / IurgNetworkVRRP

Subnet A4 for Lb / Iurg

OMCP2

OMCP1

CCP

TPGSM

Subnet A5 for AUPoIP

AUPoIP

Network

Router 5S

Router 5P

SSW1port 3

port 4port 6port 7

port 1

SSW2

port 3port 4port 6port 7

port 1

VRRP

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

3BK 17438 5004 PGZZA Ed.28 33 / 100


34/100


9130 BSC Evolution

AlarmBox

Router 2

AsigoIPNetwork

Subnet A1 for O&M Router 1

IP O&M Network

Subnet A2 for AsigoIP

Router 3

BSSoIP

Network

Subnet A3 for BSSoIP

Router 4

Lb / IurgNetwork

Subnet A4 for Lb / Iurg

OMCP2

OMCP1

CCP

TPGSM

SSW2

SSW1port 3

port 4port 6port 7

port 3port 4port 6port 7

SW1

SW2

SW3

SW4

port 1

port 1

SW5

AUPoIP

Network

Subnet A5 for AUPoIP

Router 5

Figure 8: 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, please refer to the BSS O&M RoutingConfigurationsdocument (3BK 17422 5002 PGZZA).

For the definition of the subnet A2, A3, A4 and A5, the necessary telecomparameters are set in the 9130 BSC Evolution, as shown below.

34 / 100 3BK 17438 5004 PGZZA Ed.28


35/100


Parameter name Purpose Values ApplicableSubnet

IP_Ethernet_Topology

This parameterindicates if 2 LAN

topology (with RIPprotocol) or 1 LANtopology (without RIPprotocol) is used bythe BSC in IP overEthernet case

One LAN All

IP_Extraction_ Point This parameterindicates whetherthe IP link forOMC-R and CBC isextracted/inserteddirectly at SSW

board (BSC), at theTCADAPT (IP overAter) or at the MSC(IP over Ater). Thisinformation is neededfor programming theTC-ADAPT.

Direct (theextraction pointis the BSC)

All

BSS_Transport_Mode

This parameterindicates whether the9130 BSC Evolutionuses an TDM or an

IP transport on Aterlevel.

IP transport All

IP_EXTLINK_SHARING

Indicates if the O&Mlink is shared with a9130 MFS Evolutionor not.

No All

3BK 17438 5004 PGZZA Ed.28 35 / 100


36/100



Allows the selectionof the appropriate

internal VLAN tagsto use at BSC switchlevel.

The available valuesfor this paramater are:

COMMON TAGGING

DISTINC ASIP

AUIP BSS LB

IURG

DISTINCT ASIP

AUIP BSS

DISTINCT OAM

AOIP BSS

DISTINCT OAM

TEL

Default value is

COMMON TAGGING.AllVLAN_CONF_

INDEX

A User Plane over IP (AUPoIP) flow is available withRelease B12.

ROUTING_TABLE(BSC)

Defines the list ofstatic routes. Eachroute is defined by :

the destination IP

address

the destination IP

subnet mask

the gateway IP

address

To define the IPaddresses of theRoutes towardsthe gateway(used by the BSCfor sending IPpackets to theexternal world)

All

BSC_IP_O&M_Subnet_Mask

Gives the mask of theexternal subnet A1 forO&M

Shall be higherthan or equalto 6 hosts.Default value:255.255.255.248for 6 hosts (/29 asprefix network)

A1

Start_O&M_IP_Address

Indicates the first IPaddress of the rangereserved for the BSC

in Subnet A for O&M

A1

36 / 100 3BK 17438 5004 PGZZA Ed.28


37/100



REACHABILITY_TEST_ADR _O&M

IP address to be usedby the BSC for testing

the access to theexternal network forO&M needs

IP address of thegateway used for

O&M

A1

EN_ASIG_OVER_IP

This parameterindicates whether the9130 BSC Evolutionuses an TDM or an IPA signalling.

True A2

ASIG_IP_SUBNET_MASK_BSC

Subnet mask for theA Signalling over IP(AsigoIP) subnet.

The minimumrange size is 2

A2

START_ASIG_IP_ADDRESS_BSC

Start address for theA Signalling over IP(AsigoIP) subnet. Therange size is 2

A2

REACHABILITY_TEST_ADDR_ ASIG

IP Address to beused by the BSC fortesting the access tothe external networkfor A Signalling overIP (AsigoIP) Telecom

needs

Address of thegateway usedfor A Signallingover IP (AsigoIP)Telecom needs

A2

BSS_IP_SUBNET_MASK_BSC

Subnet mask for theBSS over IP (BSSoIP)subnet.

The range size is10

A3

START_BSS_IP_ADDRESS_BSC

Start address for theBSS over IP (BSSoIP)subnet. The rangesize is 10

A3

REACHABILITY_TEST_ADDR_ BSS

IP Address to be usedby the BSC for testing

the access to theexternal network forBSS over IP (BSSoIP)telecom needs

Address of thegateway used

for BSS overIP (BSSoIP)Telecom needs

A3

EN_LB Indicates whetherMx-BSC enable Lbinterface

TRUE A4

EN_IURG Indicates whetherMx-BSC enable Iur-ginterface

TRUE A4

3BK 17438 5004 PGZZA Ed.28 37 / 100


38/100



START_ADD_FUNC_ IP_

ADDRESS_BSC

Start address forthe Lb and/or Iur-g

address range

A4

ADD_FUNC_IP_SUBNET_MASK_BSC

Subnet mask forthe subnet whereLb and/or Iur-gaddresses are located


A4

REACHABILITY_TEST_ ADDR_ADD_FUNC

IP Address to be usedby the BSC for testingthe access to theexternal network forLb and/or Iur-g over IPTelecom needs

Address of thegateway used forLb and/or Iur-gover IP Telecomneeds

A4

START_AUP_IP_ADDRESS

_BSC

First IP address forthe range of telecomaddresses shown tothe external worldfor the feature AUser Plane over IP(AUPoIP).

A5

AUP_IP_SUBNET_MASK

_BSC

Mask of the subnetwhere is allocatedthe range of BSC

addresses used fortelecom protocolsfor the feature AUser Plane over IP(AUPoIP).


A5

REACHABILITY_TEST_ADDR_AUP

The IP address to beused by the BSC fortesting the access tothe external networkfor A User Plane overIP (AUPoIP) telecomneeds. It has to be in

the same subnet asBSC Start AUP overIP Address.

Address of thegateway usedfor A User Planeover IP (AUPoIP)Telecom needs

A5

EN_AUP_ OVER_IP This parameterindicates whether the9130 BSC Evolutionuses an TDM oran IP A User Planetransport.

TRUE A5

Table 11: Telecom parameters Subnet Definition

38 / 100 3BK 17438 5004 PGZZA Ed.28


39/100


In subnet A1, to reach the BSC OMCP boards and the Alarm box fromeverywhere in the IP O&M network, the external IP addresses based on theSTART_O&M_IP_ADDRESS are set in the 9130 BSC Evolution, as shownbelow.

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 OMCPstandby plane (for O&M standbyplane reachability test)

Start_O&M_IP_Address + 3


External alarm box Start_O&M_IP_Address + 5


Table 12: External IP Addresses for O&M

For A Signaling over IP (AsigoIP), to reach the BSC OMCP boards fromeverywhere in the IP network, the external IP addresses based on theSTART_ASIG_IP_ADDRESS_BSC are set in the 9130 BSC Evolution, asshown below.

Boards IP Address

9130 BSC Evolution active OMCP Start_Asig_IP_Address_BSC


Start_Asig_IP_Address_BSC + 1

Table 13: External IP Addresses for A Signalling over IP (AsigoIP)

For A User Plane over IP (AUPoIP), to reach the BSC OMCP boards (for

reachability test) and the TPGSM from everywhere in the IP network, theexternal IP addresses based on the START_AUP_IP_ADDRESS_BSC, areset in the 9130 BSC Evolution as shown below:


9130 BSCEvolution activeOMCP

START_AUP_IP_Address_BSC

3BK 17438 5004 PGZZA Ed.28 39 / 100


40/100



9130 BSCEvolutionactive OMCP

standby plane(for Telecomstandby planereachabilitytest)


9130 BSCEvolution activeTPGSM/TPIP


RTP_IP_ADDRESS _BSC

RTP_IP_Addressaddressesof he RTPand MUXRTPTPIP data pathtermination. The

RTP function issupported by theTPIP (TPGSM)

Table 14: External IP Addresses for A User Plane over IP (AUPoIP)

For BSS over IP (BSSoIP), to reach the BSC OMCP boards, the TPGSM andthe CCP boards, from everywhere in the IP network, the external IP addressesbased on the Start_BSS_IP_Address_BSC are set in the BSC, as shown below.

Boards IP Address

9130 BSC Evolution active OMCP Start_BSS_IP_Address_BSC

9130 BSC Evolution active OMCPstandby plane (for standby planereachability test)

Start_BSS_IP_Address_BSC + 1

9130 BSC Evolution active TPGSM Start_BSS_IP_Address_BSC + 2






40 / 100 3BK 17438 5004 PGZZA Ed.28


41/100


Boards IP Address



Table 15: External IP Addresses for BSS over IP (BSSoIP)

To reach the BSC OMCP boards, the Alarm box, the CCP boards fromeverywhere in the IP Telecom network, the external IP addresses based onthe Start_Add_Func_IP_Address_BSC are set in the 9130 BSC Evolution, asshown below.

Boards IP Address

9130 BSC Evolution active OMCP Start_Add_Func_IP_Address_BSC


Start_Add_Func_IP_Address_BSC+ 1

Table 16: External IP Addresses for Lb / Iur-g over IP

The 9130 BSC Evolution flows and switch ports to be used are shown below.

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).

9130 BSC Evolution switch ports

3 7 1 6 4

VLAN_CONF _INDEX

IP Addr.Used

9130 BSC Evolution flows separation

0 12 O&M +Telecom

- Aflex-TDMO&Mpossibility

- -

1 14 O&M Telecom Aflex-TDM

O&Mpossibility

- -

2 17 O&M AoIP(AsigoIPandAUPoIP)

- BSSoIP /Lb / Iur-g

-

3BK 17438 5004 PGZZA Ed.28 41 / 100


42/100


43/100


Case failure of O&M active side then swap to the other switch side if

stand-by side is ok for telecom and send an alarm

Case failure of O&M stand-by side then send an alarm

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

Test telecom address on both active/stand-by 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 stand-by side then only send an alarm.

Arm a telecom related timer.

The term failure of telecom active/stand-by side indicates an inability to reachthe telecom address for reachability test when using the active/stand-by side.

3BK 17438 5004 PGZZA Ed.28 43 / 100


44/100


44 / 100 3BK 17438 5004 PGZZA Ed.28


45/100

3 Management of IP Transport in 9130 MFS Evolution


This section is dedicated to the IP addressing of the 9130 MFS Evolutionsubsystem

3BK 17438 5004 PGZZA Ed.28 45 / 100


46/100


3.1 LAN Configuration

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

3.2 IP Addressing Rules

IP addresses for a 9130 MFS Evolution can be chosen freely, limited only bythe following rules:

9130 MFS Evolution external addresses must not belong to the followingnetwork:

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


Geographical Address and can have the value 3 or 4.

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

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


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 the 9130 MFS Evolution.

3.3 Several Subnets for Separate O&M and Telecom

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

46 / 100 3BK 17438 5004 PGZZA Ed.28


47/100


It is possible to have, at most, one subnet for O&M flow and one subnet foreach Telecom flow, as shown in the following figure.

9130 MFS Evolution

Router 1

Subnet A for O&M

Router 1

Subnet Gb

Router 1

Router 1

Subnet BSS/IPGSL

Subnet BSS/IPGCH

IP O&M Network

IP GbTelecom

Network

IP BSS Telecom

Network (IPGSL)

IP BSS Telecom

Network (IPGCH)

SSW2

CS

A

CS

B

GPUs

SSW1

The O&M interface on the existing access router can also be configuredfor the telecom flow.

Other possible Telecom subnets configurations:

Two subnets:O&M subnet

Telecom subnet (with all the Telecom flows)

Three subnets:

O&M subnet

Gb subnet

BSS subnet (IPGSL and IPGCH functions)

Four Subnets:

O&M subnet

Gb subnet

IPGSL subnet

IPGCH subnet

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

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

Two subnets:

O&M subnet

3BK 17438 5004 PGZZA Ed.28 47 / 100


48/100


BSS subnet (IPGSL or IPGCH flows or both)

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

48 / 100 3BK 17438 5004 PGZZA Ed.28


49/100


The necessary parameters for this LAN configuration are set in the 9130 MFSEvolution, as shown below.


Enable RIPv2 Indicates whether a one

LAN (no RIP) or twoLAN (RIP) solution isused

No

ROUTING_TABLE(MFS)

Defines the list ofstatic routes. Eachroute is defined by:the destination IPaddress, the destinationIP subnet mask, thegateway IP address

IP addresses of theroutes towards thegateway

VLAN_CONF_INDEX(MFS) Allows the selection ofthe appropriate internalVLAN tags to use atMFS SW level

Default value is 0 -common O&M / telecomtagging.

Table 19: Parameters for LAN Configuration

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

MFS switch ports

3 7 6 5

VLAN_CONF_INDEX

(MFS)

MFS flows separation

0 O&M +Telecom

- - -

1 O&M Telecom - -

2 O&M GboIP BSSoIP -

3 O&M GboIP IPGSL IPGCH

Table 20: The MFS flow and switch ports

For the definition of the subnet A, the necessary O&M parameters are set in the9130 MFS Evolution, as shown below.


MFS_IP_Address IP address to be usedby OMC-R to reach theMFS. Set from OMC-R.

3BK 17438 5004 PGZZA Ed.28 49 / 100


50/100



Netmask floatingaddress (through themfssetup command)

Gives the mask of theexternal subnet for O&M9130 MFS Evolution


IP address to be used bythe 9130 MFS Evolutionfor testing the access tothe external network forO&M needs

Table 21: Parameters for the Definition of Subnet A

For the definition of the subnet Gb, the necessary telecom parameters areset in the 9130 MFS Evolution, as shown below.


GB_Transport_ Mode Indicates whether thetelecom function uses aTDM or IP transport onGb

IP transport

IPGB_SUBNET_MASK_MFS

Gives the mask ofthe external subnetfrom O&M 9130 MFSEvolution

Should be higher orequal to 32 hosts (>=

/27)

Default value:255.255.255.224

REACHABILITY_TEST_ADR_ TEL _GB

IP address to be used bythe 9130 MFS Evolutionfor testing the access tothe external network forGb flow needs

REACHABILITY_TEST_ADDR_TEL_GB_GPU

IP address to be used bythe GPU for testing theaccess to the externalnetwork for Gb telecomneeds.

Table 22: Telecom Parameters for the Definition of Subnet Gb

Use the following table to obtain the GPU IP addresses in the Gb subnet (inthis example GB_Gb_Base_IP is 10.102.111.193).

50 / 100 3BK 17438 5004 PGZZA Ed.28


51/100


52/100


No. Example IPAddress (/27subnet)

AutomatedIP AddressAllocation

GPU LogicalNumbering

Comment /Options

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 GatewayIP Address

22 10.102.111.214 GPU_GB_Base_IP+ 21


23 10.102.111.215 GPU_GB_Base_IP+ 22

GPU 25 -

24 10.102.111.216 GPU_GB_Base_IP+ 23

GPU 26 -

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 - - -

31 10.102.111.223 - - broadcast

Table 23: IP-Adressing inside MFS for Gb-over-IP table

The Gateway IP address allocation:

For upper shelf is one of the follwing:

GPU_Gb_Base_IP + 6

GPU_Gb_Base_IP + 7

For lower shelf is one of the follwing:

GPU_Gb_Base_IP + 20

52 / 100 3BK 17438 5004 PGZZA Ed.28


53/100


GPU_Gb_Base_IP + 21

For the definition of the subnet BSS/IPGSL, the necessary telecom parametersare set in the 9130 MFS Evolution, as shown below.


BSS_Transport _ Mode(MFS)

Indicates whether MFSuses an TDM or an IPtransport on GSL leveland IPGCH

IP transport

IPBSS_SUBNET_MASK_MFS

Gives the mask of theexternal subnet for BSSTelecom (IPGCH/GSL)9130 MFS Evolutionaddress.


/27)

Default value:255.255.255.224.

IPGSL_Base_Address_MFS

Starting GPU IPGSLaddress.

REACHABILITY_TEST_ADDR_TEL_GSL

IP address to be used bythe 9130 MFS Evolutionfor testing the access tothe external network forIPGSL telecom needs

REACHABILITY_TEST_ADDR_TEL_GSL_GPU

IP address to be used bythe GPU for testing theaccess to the externalnetwork for IP GSLtelecom needs.

Table 24: Telecom Parameters for Definition of Subnet BSS/IPGSL

Use the following formula to obtain the GPU IP addresses in the correspondingBSS/IPGSL subnet .

3BK 17438 5004 PGZZA Ed.28 53 / 100


54/100


Configuration GPU IP address

9 GPU IPGSL_Base_Address_MFS + Y 1

Where Y is the GPU physical slotnumber

16 GPU or 21 GPU IPGSL_Base_Address_MFS + (X 3) * 14 + Y 1

Where

X is the geographical shelf

address

Yis the GPU logical slot number

Table 25: IP Assignment Rules in the BSS/IPGSL Subnet

54 / 100 3BK 17438 5004 PGZZA Ed.28


55/100


For the definition of the subnet BSS/IPGCH, the necessary telecom parametersare set in the 9130 MFS Evolution, as shown below.


BSS_Transport_ Mode Indicates whether MFS

uses an TDM or an IPtransport on GSL leveland IPGCH

IP transport

IPBSS_SUBNET_MASK_MFS

Gives the mask of theexternal subnet for BSSTelecom (IPGCH/GSL)9130 MFS Evolutionaddress.


/27)

Default value:255.255.255.224.

IPGCH_Base_Address_MFS

Starting GPU IPGCHaddress.

REACHABILITY_TEST_ADDR_ IPGCH

IP address to be used bythe 9130 MFS Evolutionfor testing the access tothe external network forIPGCH telecom needs.

REACHABILITY_TEST_ADDR_IPGCH_GPU

IP address to be used bythe GPU for testing theaccess to the externalnetwork for IPGCHtelecom needs.

Table 26: Telecom Parameters for Definition of Ssubnet BSS/IPGCH

Use the following formula to obtain the GPU IP addresses in the correspondingBSS/IPGCH subnet.

3BK 17438 5004 PGZZA Ed.28 55 / 100


56/100


Configuration GPU IP address

9 GPU IPGCH_Base_Address_MFS + Y 1

Where Y is the GPU physical slotnumber

16 GPU or 21 GPU IPGCH_Base_Address_MFS + (X 3) * 14 + Y 1

Where

X is the geographical shelf

address

Yis the GPU logical slot number

Table 27: IP Assignment Rules in the BSS/IPGCH Subnet

Each host in the MFS (control stations and GPUs) must get routing information:gateway addresses (there can be one gateway per subnet used) andassociated subnet. The control stations have to distribute the information toeach GPU (active and spare).

The MFS routing table is configured from the IMT.

To change 9130 MFS IP address plan, use Change IP Address Plan, inthecase of9130 MFS Evolution IP addressing plan change.

56 / 100 3BK 17438 5004 PGZZA Ed.28


57/100


3.4 Reachability Test

In order to have an efficient test, the reachability address should be the firstaddress encountered out of the MFS for the O&M, Gb, IPGSL or IPGCHflow. The farther is the address, the higher is the risk to uselessly changethe Ethernet plan (higher probability to have the failure beyond the edge

switch/router, making the change of Ethernet plane inefficient).

To test the reachability for the different physical links, set the followingparameters according to theReachability Test Rules (Section 3.4.4):

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 (Section 3.4.1)

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 fortelecom needs; please refer to Telecom Reachability Test by the Control

Station(Section 3.4.2)

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 GPU

(Section 3.4.3)

REACHABILITY_ PERIODICITY (optional).

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

from aL2 network perspective, where the device for which the reachability

is tested is in the same network with the target

from aL3 network perspective, where the device for which the reachability is

tested is not in the same network with the target

3.4.1 O&M Reachability Test

The tests purpose is to manage the Ethernet plan by switching the active /

stand-by plans in the case of an active plan failure.Both active and stand-by sides are supervised and associated alarms sent.The stand-by plan is supervised to allow stand-by plan repair before a possiblefailure of the active plan. The alarm indicates the concerned control stationboard and switch plane. An active switch side failure is detected via the arpcache expiration (1 minute by default). If both switch sides are down for theactive control station, a switchover is not performed since the associated alarmwould 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

3BK 17438 5004 PGZZA Ed.28 57 / 100


58/100


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.

Parameter name L2 network L3 network

REACHABILITY_TEST_ADDR_O&M (MFS)

The IP address of theOMC

The IP address of therouter O&M interface

Table 28: The O&M Reachability Test Address

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

CSactive

GPU

O&M

SW1 SW2active standby

supervision test

traffic & supervision test

Figure 9: 9130 MFS Evolution O&M reachability test

3.4.2 Telecom Reachability Test by the Control Station

The test of the telecom reachability address used by the control station is donefor supervision purpose. Both active and stand-by sides are supervised andassociated alarms sent. The alarm indicates the concerned control stationboard and switch plane. A failure on telecom address does not lead to thecontrol station swap to the other switch side.

The control station has an IP address in every telecom subnet.

Recommended rules:

58 / 100 3BK 17438 5004 PGZZA Ed.28


59/100



address encountered out of the MFS for the telecom flow

In the case of an 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.

REACHABILITY_TEST_ADDR_TEL_GB (MFS) cannot be configured whenGPU_Gb_Base_IP is not configured

REACHABILITY_TEST_ADDR_TEL_GSL (MFS) cannot be configured whenIPGSL_Base_Address_MFS is not configured

REACHABILITY_TEST_ADDR_TEL_IPGCH (MFS) cannot be configuredwhen IPGCH_Base_Address_MFS is not configured.


REACHABILITY_TEST_ADDR_ TEL_GB(MFS)

The IP address of oneSGSN

The IP address of theGb over IP interface ofthe router

REACHABILITY_TEST_ADDR_TEL_GSL (MFS)

The telecom IP addressof the BSC

The IP address of theIPGSL interface of therouter

REACHABILITY_TEST_ADDR_TEL_IPGCH (MFS)

The first IP addressencountered out of theMFS for the IPGCH flow

The IP address of theIPGCH interface of therouter

Table 29: Control Station Telecom Reachability Test Address

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

3BK 17438 5004 PGZZA Ed.28 59 / 100


60/100


CSactive

GPU

Telecom


supervision test

Figure 10: 9130 MFS Evolution Telecom Reachability Test by Control Station

3.4.3 Telecom Reachability Test by GPU

The test of the telecom reachability address used by the GPU is done for trafficdefence purposes on its active side. The GPU is able to swap to the stand-byside if needed. If both sides are down, the GPU alarms.

Each GPU is independent in terms of switching side decisions.

Recommended rules:


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

REACHABILITY_TEST_ADDR_TEL_GB_GPU (MFS) cannot be configuredwhen GPU_Gb_Base_IP is not configured

REACHABILITY_TEST_ADDR_TEL_GSL_GPU (MFS) cannot be configuredwhen IPGSL_Base_Address_MFS is not configured

REACHABILITY_TEST_ADDR_TEL_IPGCH_GPU (MFS) cannot beconfigured when IPGCH_Base_Address_MFS is not configured.

60 / 100 3BK 17438 5004 PGZZA Ed.28


61/100



REACHABILITY_TEST_ADDR_TEL_GB_GPU (MFS)

The IP address of oneSGSN

The IP address of theGb over IP interface ofthe router

REACHABILITY_TEST_ADDR_TEL_GSL_GPU (MFS)

The telecom IP addressof the BSC

The IP address of theIPGSL interface of therouter

REACHABILITY_TEST_ADDR_TEL_IPGCH_GPU(MFS)

The first IP addressencountered out of theMFS for the IPGCH flow

The IP address of theIPGCH interface of therouter

Table 30: GPU Telecom Reachability Test Address

CSactive

GPU

Telecom


traffic defense test

Figure 11: 9130 MFS Evolution Telecom Reachability Test by GPU

3.4.4 Reachability Test Rules

Depending on the following topology, set the reachability parameters:

No Flow Separation(Section 3.4.4.1)

O&M and Telecom Flows Separation(Section 3.4.4.2)

O&M, Gb and BSS Flows Separation(Section 3.4.4.3)

Full Flows Separation(Section 3.4.4.4)

3BK 17438 5004 PGZZA Ed.28 61 / 100


62/100


63/100


Set the following parameters used by GPU :

If GB over IP is activated, set REACHABILITY_ TEST_ADDR_

TEL_GB_GPU (MFS) and, optional, REACHABILITY_ TEST_LABEL_

TEL_GB_GPU (MFS)

IfBSS over IPis 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.

3.4.4.3 O&M, Gb and BSS Flows Separation

This topology is valid only if GB over IPand BSS over IPare 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 parametersbelow 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_ADDR_ TEL_IPGCH_GPU (MFS) and, optional,

REACHABILITY_ TEST_LABEL_ TEL_IPGCH_GPU (MFS)


3BK 17438 5004 PGZZA Ed.28 63 / 100


64/100


3.4.4.4 Full Flows Separation

This topology is valid only if GB over IPand BSS over IPare activated.

Set the following parameters used by 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 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_ADDR_ TEL_IPGCH_GPU (MFS) and, optional,

REACHABILITY_ TEST_LABEL_ TEL_IPGCH_GPU (MFS)


64 / 100 3BK 17438 5004 PGZZA Ed.28


65/100

4 Management of IP Transport in 9135 MFS


This section is dedicated to the IP addressing of the 9135 MFS subsystem

3BK 17438 5004 PGZZA Ed.28 65 / 100


66/100


4.1 LAN Configuration

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

The Gb over IP on Gb interface with SGSN is the only telecom flow.

9135 MFS with DS10 control station equipped with Alcatel-Lucent OmniStack

LS 6224 switches

The O&M router is connected to the both control station and the Gb overIP router (Telecom router) is connected to the both switch boards. Soonly segregation of flux configuration (O&M subnet and Gb over IP subnet)is supported.

4.2 Both the O&M and the Telecom flows in IP

The necessary parameters for this LAN configuration are set in the 9135MFS, as shown below.


Enable RIPv2 Indicates whether a oneLAN (no RIP) or twoLAN (RIP) solution isused

No

ROUTING_TABLE(MFS)

Defines the list ofstatic routes. Eachroute is defined by:the destination IPaddress, the destinationIP subnet mask, thegateway IP address

IP addresses of theroutes towards thegateway


For the definition of the subnet Gb, the necessary telecom parameters are setin the 9135 MFS, as shown below


GB_Transport_ Mode Indicates whether thetelecom function uses a

TDM or IP transport onGb

IP transport

IPGB_SUBNET_MASK_MFS

Gives the mask of theexternal subnet for GbTelecom 9135 MFSaddresses


/27)

Default value:255.255.255.224

66 / 100 3BK 17438 5004 PGZZA Ed.28


67/100



GPU_Gb_Base_IP Base address of theIP address of thelocal Gb IP endpoint,

used to define theGPU_Gb_IP_Addressof each GPU board (forGb over IP interface)and also used to definean IP address on eachCS board

Routing_Table Defines the list of staticroutes. Each route isdefined by

the destination IP

address

the destination IP

subnet mask

the gateway IP

address

To define the IPaddresses of the routestowards the gateway

Table 32: Telecom Parameters for the Definition of Subnet Gb

Use the following table to obtain the GPU IP addresses in the Gb subnet (inthis example GB_Gb_Base_IP is 10.102.111.193).




Comment /Options

0 10.102.111.192 - - subnet IP address

1 10.102.111.193 GPU_GB_Base_IP+ 0

GPU 1 GPU_Gb_Base_IP

2 10.102.111.194 GPU_GB_Base_IP+ 1

GPU 2 -

3 10.102.111.195 GPU_GB_Base_IP+ 2

GPU 3 -

4 10.102.111.196 GPU_GB_Base_IP+ 3

GPU 4 -

5 10.102.111.197 GPU_GB_Base_IP+ 4

- shall be kept freefor spare

6 10.102.111.198 GPU_GB_Base_IP+ 5

- -

3BK 17438 5004 PGZZA Ed.28 67 / 100


68/100





Comment /Options

7 10.102.111.199 GPU_GB_Base_IP

+ 6

- possible Gateway

IP Address

8 10.102.111.200 GPU_GB_Base_IP+ 7


9 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


22 10.102.111.214 GPU_GB_Base_IP+ 21


23 10.102.111.215 GPU_GB_Base_IP+ 22

GPU 25 -

24 10.102.111.216 GPU_GB_Base_IP

+ 23

GPU 26 -

68 / 100 3BK 17438 5004 PGZZA Ed.28


69/100





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 forVRRP

31 10.102.111.223 - - broadcast

Table 33: IP-Adressing inside MFS for Gb-over-IP table

To change 9135 MFS IP address plan, use Change IP Address Plan, inthecase ofChange 9135 MFS IP parameters for separate O&M and Telcom IPflows configuration.

3BK 17438 5004 PGZZA Ed.28 69 / 100


70/100


70 / 100 3BK 17438 5004 PGZZA Ed.28


71/100

5 Management of IP Transport in 9125 TC


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

3BK 17438 5004 PGZZA Ed.28 71 / 100


72/100


73/100



IP address of the TCSLlink on TC side.

Floating TCSL IPaddress used byTC to communicate

to 9130 EvolutionBSCs.

TCSL Target IP Address

Note: If no flow separation is selected, thevalue for TCSL Target IP Addressmust be the same with TCIF Active IPAddress.

TRAUP IP Address IP address of the TC,used for IPTCH flow(MUXTRAUP) and forTC-TC flow (eTRAUP)

-

M2UA TC IP Address SG1 IP address of the TCon the processor SG1,used for IP_BSSAsig flow(M2UA/SCTP signallingbetween BSC and TCand coming from/going toA interface).

The traffic isbetween BSC andTC.

Address usedon TC by thetwo processorsPower Quick3 withsignalling gatewayfunction.

IP address of the TCon the processor SG2,

used for IP_BSSAsig flow(M2UA/SCTP signallingbetween BSC and TCand coming from/going toA interface).

The traffic isbetween BSC and

TC.

Address usedon TC by thetwo processorsPower Quick3 withsignalling gatewayfunction

M2UA TC IP Address SG2

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 beincremented).

NTP1 Server Address Address of NTP servernumber 1

-


-


-

3BK 17438 5004 PGZZA Ed.28 73 / 100


74/100



External OAM Router IP address to be usedby the TC for testing theaccess to the external

network for O&M needs

-

External OAM Mask Gives the mask ofthe subnet where isallocated the range of TCaddresses used for O&M

To be defined asthe size of theTelecom Subnet :shall be higher thanor equal to 6 hosts(encoded in 3 bits).=> default value:255.255.255.248for 6 hosts (/29 asprefix Network)

External Telecom Router IP address to be usedby the TC for testing theaccess to the externalnetwork for telecomneeds.

-

External Telecom Mask Gives the mask ofthe subnet where isallocated the range ofTC addresses used fortelecom protocols

To be defined asthe size of theTelecom Subnet:shall be higher thanor equal to 6 hosts(encoded in 3 bits).

=> default value:255.255.255.248for 6 hosts (/29 asprefix Network)

Internal IP NetworkAddress

IP Address for internalnetwork

-

Internal IP Network Mask Gives the mask of theinternal IP network

-

VLAN Separation Allows the selection ofthe appropriate internal

VLAN tags to use at TCSW level.

Default, checkboxis unchecked, no

flow segregation.


74 / 100 3BK 17438 5004 PGZZA Ed.28


75/100


The TC flows and ports to be used:

TCIF ports

RJ2-x RJ1-x

VLAN Separation

Where x is TCIF slot (0, 1)

checkbox is unchecked O&M + Telecom O&M + Telecom

checkbox is checked O&M Telecom

Table 35: The TC flow and ports

To change the 9125 TC IP address plan, use Change IP Address Plan, in thecase of 9125 TC IP addressing plan change.

3BK 17438 5004 PGZZA Ed.28 75 / 100


76/100


5.1.1 O&M and Telecom with One Shared Subnet

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

9125 TC

TCIF1

RJ20

RJ21

Router 1

Router 2

VRRPTCIF2


Subnet A

Figure 12: 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 canbe higher than 60kpps with 1500-byte packets.

76 / 100 3BK 17438 5004 PGZZA Ed.28


77/100


5.1.2 Two Subnets for Separate O&M and Telecom

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

9125 TC

TCIF1

RJ20

Router 1

Router 2

VRRP

TCIF2

IP O&M Network

Subnet A

RJ10

Router 1

Router 2

VRRP

IP Telecom Network

Subnet B

RJ21

RJ11

Figure 13: Two Subnets for Separate O&M and Telecom

5.2 Reachability Test

The TCIF performs a reachability test:

An ICMP ping request of a O&M address

REACHABILITY_TEST_ADDR_O&MThe default period for O&M is 30 seconds.

An ARP request of a telecom address ( if the telecom feature is activated):

REACHABILITY_TEST_ADDRESS_TELThe 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 flowis available, the O&M flows is defended. Also, the stand-by TCIF performsreachability test in order to report the link status to the active TCIF.

3BK 17438 5004 PGZZA Ed.28 77 / 100


78/100


79/100

6 Management of IP Transport in 9100 BTS


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

3BK 17438 5004 PGZZA Ed.28 79 / 100


80/100


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

Note: IPoE1 feature is available with Release B12.

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

BTS A

BTS B

9130 BSC

Evolution

IPoE1

IPoE1


Subnet E

IP

IP

Figure 14: BTS IP in IPoE1 Configuration

The necessary parameters for this LAN configuration are shown below.


IP_Ethernet_Topology Indicates whether a oneLAN or two Lan solutionis used.

One LAN

BSS_Transport_Mode Indicates whether BSCuses an TDM or an IPtransport on Ater level.

Telecom transport

BTS_IP_Interface-used Indicates which BTSIP interface is used.Directly deduces byBSC from the Abistopology.

IP over E1

BTS_IP_Identifier andBTS_IP_Identifier_Length

Used by BTS and DHCPin order to determinethe IP BTS

String. By defaultQMUX addressconverted in string.

80 / 100 3BK 17438 5004 PGZZA Ed.28


81/100



DHCP_Location Specifies for an IP BTSif the DHCP server islocated in the OMC-R

or not.

DHCP located in theOMC-R.

DHCP_SERVER_IP_ADDRESS

Spe

bss telecom routing 174385004e28.pdf

Documents