BSC IP Application Set Up: User Guide

BSC IP Application Set Up
USER GUIDE
7/198 17-APT 210 09 Uen T

Copyright
© Ericsson AB 2013, 2014, 2016. All rights reserved. No part of this document
may be reproduced in any form without the written permission of the copyright
owner.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.
Trademark List
Ericsson is the trademark or registered trademark of

Telefonaktiebolaget LM Ericsson.
All other trademarks mentioned herein are the property of their respective
owners.
7/198 17-APT 210 09 Uen T | 2016-06-03

Contents
Contents
1 General Information 1
1.1 Introduction 1
1.2 Revision Information 1
1.3 Typographic Conventions 2
2 Prerequisites 5
3 Principles and Example Configurations 7

3.1 General 7
3.2 Subnet and VLAN Structure 7
3.3 IP Devices 8
3.4 Gateway IP Addresses and IP Supervision 9
3.5 R-PMO, RTT, GMLog, and OEN 13
3.6 Gb over IP 16
3.7 Packet Abis over IP 17
3.8 A-Interface over IP 19
3.9 SIGTRAN 21
3.10 SMS CBC 25
3.11 Network Time Protocol on SCX 26
4 IP Consistency Check 29
4.1 Verify IP Connectivity to the BSC IP Infrastructure 29
4.2 IP Configuration Consistency Check 29
5 Concepts 31
Glossary 33
Reference List 35
7/198 17-APT 210 09 Uen T | 2016-06-03

7/198 17-APT 210 09 Uen T | 2016-06-03

General Information
1 General Information
1.1 Introduction
This User Guide provides information to set up support for the IP applications:
• Gb over IP
• Packet Abis over IP
• A-Interface over IP
• SIGTRAN (SS7 over IP)
• GPRS Mobile Logging (GMLog)
• BSC Internal IP Gateway Supervision (IPS)
• Open Event Notification Interface (OEN)
• Real-Time Performance Monitoring (R-PMO)
• Real Time Trace (RTT)
• Short Message Service Cell Broadcast Center (SMS CBC)
• Network Time Protocol (NTP) for Evo Controller 8200/BSC
The reader of this document is expected to be familiar with the BSC IP

Infrastructure and the BSC applications using IP connectivity. The knowledge
needed is found in Reference [1], , Reference [4], Reference [7], Reference
[16], Reference [19] and Reference [20].
For further information relating to recommended IP addressing schemes, see

Reference [6].
1.2 Revision Information

The changes introduced in revision K (G10B) are the following:
• The port range for A-Interface over IP is updated with a range for
multiplexed traffic. See Section 3.8.2 on page 20.
The changes introduced in revision L (G11B) are the following:
• A clarification is added that IPDEVNO is not used for the “floating” IP

address for Abis over IP, see Section 3.7.1 on page 17. The “floating” IP
address is also added in the example in Section 3.7.3 on page 18 and
Section 3.7.4 on page 19.
7/198 17-APT 210 09 Uen T | 2016-06-03 1

• SMS CBC is added.
The change introduced in revision M (G12B) is the following:
• Updates for Evo Controller 8200.
The changes introduced in revision M1 (G12B) are the following:
• Restructured document to make it easier to use for specific IP applications.
• Introduced NTP on SCX.
The change introduced in revision M2 (G12B) is the following;
• Correct minor link errors in the reference list.
The changes introduced in revision N1 (G13B) are the following;
• Added RP application Combined Traffic Handler.
• Correct minor link errors in the reference list.
• BSC shall be set as “client” when using Sigtran on CP.
• RTT added.
The change introduced in revision N2 (G13B) is the following;
• Updated example for Evo Controller 8200 in chapter Section 3.8.3 on

page 20.
The change introduced in revision N3 (G13B) is the following;
• Corrected example for Evo Controller 8200 in chapters Section 3.7.3 on

page 18 and Section 3.8.3 on page 20.
The changes introduced in revision N4 (G13B) are the following:
• Removed Mobile@Home information
• Added information regarding separate subnets for Sigtran on CP
The change introduced in revision N5 (G14B) is the following:
• Updated references for XOS 16.1
The change introduced in revision T (G15B) is the following:
• Updated due to administrative reasons
1.3 Typographic Conventions

Command entered using a Command Line Interface (CLI) is in bold:
2 7/198 17-APT 210 09 Uen T | 2016-06-03

General Information
command text
Some command lines are too long to fit the format of this document. They are
written on multiple lines with a backslash \ character as a line continuation
marker.
rripi:ipaddr=172.30.38.11,IPDEVTYPE=RTIPGPH,\
bestbw,mask=255.255.255.240;
Note: The line continuation character is not entered, instead, the command is
entered as a single line to the CLI.
System response is formatted as:
system response.
7/198 17-APT 210 09 Uen T | 2016-06-03 3

4 7/198 17-APT 210 09 Uen T | 2016-06-03

Prerequisites
2 Prerequisites
1. The BSC IP Infrastructure must be configured as described in Reference

[9] or Reference [10], depending on which IP network interface type that
is used.
2. The BSC IP Infrastructure must have functioning IP connectivity to the OSS.
3. If Gb over IP is installed, the BSC IP Infrastructure must have functioning

IP connectivity to the SGSN nodes.
4. If Packet Abis over IP is installed, the BSC IP Infrastructure must have

functioning IP connectivity to the STN nodes.
5. If A-Interface over IP is installed, the BSC IP Infrastructure must have

functioning IP connectivity to a Media Gateway (MGW) in the Core Network
(CN).
6. If SIGTRAN is installed, the BSC IP Infrastructure must have functioning

IP connectivity to the signalling network nodes.
7. If SMS CBC is installed, the BSC IP Infrastructure must have functioning

IP connectivity to the CBC server.
8. The network plan, that is the subnet numbers and host number allocations
for the BSC, must be known. This includes the IP addresses of the Gb over
IP application, Abis over IP application, SIGTRAN, the O&M applications
R-PMO, RTT, GMLog, SMS CBC application, and OEN. See Reference [6]
for more information.
7/198 17-APT 210 09 Uen T | 2016-06-03 5

6 7/198 17-APT 210 09 Uen T | 2016-06-03

Principles and Example Configurations
3 Principles and Example Configurations
3.1 General
As a means to show the principles of the BSC IP application setup, an example
configuration is used. The example configuration described in this section is a
type 1 external network configuration supported by both the BSC LAN Switch
and the BSC NWI-E (see Reference [10] for more information).
3.2 Subnet and VLAN Structure

The VLAN configuration below is used to illustrate the setup of BSC IP
applications.
Note: IP subnet addresses and sizes are fully configurable.
Table 1 Allocated subnets and IP addresses for BSC LAN Switch used in
the example
VLAN name IP subnet A-side switch IP B-side switch
address IP address
SR_Gb 10.40.16.0/29 10.40.16.3 10.40.16.4
SR_OM 10.40.32.0/29 10.40.32.5 10.40.32.6
SR_Abis 10.40.48.0/29 10.40.48.3 10.40.48.4
SR_SS7 10.40.52.0/29 10.40.52.3 10.40.52.4
SR_A_userplane 10.40.81.0/29 10.40.81.3 10.40.81.4
SR_CBC 10.40.90.0/29 10.40.90.3 10.40.90.4
GbIP 172.30.12.0/25 172.30.12.1 172.30.12.2
OM_BSC 172.30.38.0/28 172.30.38.1 172.30.38.2
AbisIP 172.30.74.0/26 172.30.74.1 172.30.74.2
SS7 172.30.78.0/28 172.30.78.1 172.30.78.8
A_userplane 172.30.81.0/28 172.30.81.1 172.30.81.2
CBC 172.30.90.0/29 172.30.90.1 172.30.90.2
IPS, A-side 192.168.0.0/24 192.168.0.1 -
IPS, B-side 192.168.1.0/24 - 192.168.1.1
Intercon 192.168.2.0/30 192.168.2.1 192.168.2.2
7/198 17-APT 210 09 Uen T | 2016-06-03 7

Table 2 Allocated subnets and IP addresses for NWI-E used in the example
Subnet name IP subnet A-Side switch IP B-Side switch
address IP address
SR_Gb 10.40.16.0/29 10.40.16.3 10.40.16.4
SR_OM 10.40.32.0/29 10.40.32.5 10.40.32.6
SR_Abis 10.40.48.0/29 10.40.48.3 10.40.48.4
SR_SS7 10.40.52.0/29 10.40.52.3 10.40.52.4
SR_A_userplane 10.40.81.0/29 10.40.81.3 10.40.81.4
SR_CBC 10.40.90.0/29 10.40.90.3 10.40.90.4
Internal_OM 172.30.38.0/28 172.30.38.1 172.30.38.2
Internal_Gb 172.30.12.0/25 172.30.12.1 172.30.12.2
Internal_Abis 172.30.74.0/26 172.30.74.1 172.30.74.2
Internal_SS7 172.30.78.0/28 172.30.78.1 172.30.78.8
Internal_A 172.30.81.0/28 172.30.81.1 172.30.81.2
Internal_CBC 172.30.90.0/29 172.30.90.1 172.30.90.2
Internal_IPS 192.168.0.0/23 192.168.0.1 192.168.1.1
Internal_Intercon 192.168.2.0/30 192.168.2.1 192.168.2.2
The IP addresses of the BSC IP network in the tables above conforms to the
allocation scheme proposed in Reference [6]. If the BSC is using IP network
interfaces and you have login access, it is possible to retrieve your specific
VLAN configuration using the command:
show vlan
Note: In the configuration of the BSC LAN switch, there is a one-to-one

relation between a VLAN and an IP subnet. In the configuration of
the BSC NWI-E, there is a one-to-many relation between a VLAN and
IP subnets.
3.3 IP Devices
In this example configuration, it is assumed the BSC has:
• Two GPH RPs
• Three PGW RPs
• Two PGH RPs
• Three AGW RPs
• Three CTH RPs
8 7/198 17-APT 210 09 Uen T | 2016-06-03

The IP devices are:
• RTIPGPH-0 to RTIPGPH-1
• RTIPPGW-0 to RTIPPGW-2
• RTIPPGH-0 to RTIPPGH-1
• RTIPAGW-0 to RTIPAGW-2
• RTIPCTH-0 to RTIPCTH-2
Note: This example is only for description purpose. It is not possible to define
CTH RPs in the same BSC as PGW RPs or AGW RPs.
3.4 Gateway IP Addresses and IP Supervision
3.4.1 Gateway IP Addresses
Two gateway IP addresses must be configured, one for each BSC IP network
interface. The IP addresses must be the IP address of the BSC IP network
interfaces in the IPS subnet. In this example configuration, this means that
gateway 1 (GW1) must have IP address 192.168.0.1 and gateway 2 (GW2)
must have IP address 192.168.1.1.
In addition, if SIGTRAN is used, two additional gateways have to be defined

for the use of the SIGTRAN application. These gateways shall have their IP
addresses in the SS7 subnet.
Logically the IPS and SS7 subnets may be seen as having an A-side and
B-side. This corresponds to the way IPS monitors the respective gateway and
the use of path separation for SIGTRAN. See Reference [6] for more details.
It is very important to get the gateways defined on the correct BSC IP network
interface, as the IPS application monitors the A-side switch using plane A, and
the B-side switch using plane B. The Sigtran Link Interface (SLI) board uses the
gateways on the very same side to which it is connected.
3.4.2 IP Gateway Supervision

The IP Gateway Supervision (IPS) application monitors the connection between
the interfaces of each IP device and the two IP network interfaces. In case of
a connection failure, the IP addresses of all other applications on the failing
RP interface are either moved to the other interface of the same IP device or
moved to another IP device, depending on how the IP address redundancy
has been configured.
7/198 17-APT 210 09 Uen T | 2016-06-03 9

3.4.3 IP Addresses
All IP addresses of the IPS application must be bound to specific IP devices,

that is, the IPDEV parameter of the RRIPI command shall be used. As each IP
device has two Ethernet interfaces, two IP addresses need to be configured
for each IP device. To ensure that the IP addresses of a particular IP device
use different Ethernet interfaces, one IP address must be configured to use
GW1 and the other GW2. IP addresses for IPS must be within the IP range of
the IPS subnet.
The following IP addresses and associated gateways are used in this example
configuration:
Table 3 IP Address and Gateway per IP Device exemplified for BSC LAN
Switch
IP device IP address Network mask Gateway
RTIPGPH-0 192.168.0.2 255.255.255.0 GW1
RTIPGPH-0 192.168.1.2 255.255.255.0 GW2
RTIPGPH-1 192.168.0.3 255.255.255.0 GW1
RTIPGPH-1 192.168.1.3 255.255.255.0 GW2
RTIPPGW-0 192.168.0.66 255.255.255.0 GW1
RTIPPGW-0 192.168.1.66 255.255.255.0 GW2
RTIPPGW-1 192.168.0.67 255.255.255.0 GW1
RTIPPGW-1 192.168.1.67 255.255.255.0 GW2
RTIPPGW-2 192.168.0.68 255.255.255.0 GW1
RTIPPGW-2 192.168.1.68 255.255.255.0 GW2
RTIPPGH-0 192.168.0.130 255.255.255.0 GW1
RTIPPGH-0 192.168.1.130 255.255.255.0 GW2
RTIPPGH-1 192.168.0.131 255.255.255.0 GW1
RTIPPGH-1 192.168.1.131 255.255.255.0 GW2
RTIPAGW-0 192.168.0.180 255.255.255.0 GW1
RTIPAGW-0 192.168.1.180 255.255.255.0 GW2
RTIPAGW-1 192.168.0.181 255.255.255.0 GW1
RTIPAGW-1 192.168.1.181 255.255.255.0 GW2
RTIPAGW-2 192.168.0.182 255.255.255.0 GW1
RTIPAGW-2 192.168.1.182 255.255.255.0 GW2
RTIPCTH-0 192.168.0.190 255.255.255.0 GW1
RTIPCTH-0 192.168.1.190 255.255.255.0 GW2
RTIPCTH-1 192.168.0.191 255.255.255.0 GW1
10 7/198 17-APT 210 09 Uen T | 2016-06-03

IP device IP address Network mask Gateway

RTIPCTH-1 192.168.1.191 255.255.255.0 GW2
RTIPCTH-2 192.168.0.192 255.255.255.0 GW1
RTIPCTH-2 192.168.1.192 255.255.255.0 GW2
Note: When using NWI-E the network mask in the table above is
255.255.254.0 for all rows.
3.4.4 Configure IP Service

Follow the instructions in Reference [23] and configure:
1. Gateway IP addresses
2. IP addresses for IPS. Gateway and IP device must be defined for each
IP address.
In this example set up, the IPS subnet is a /23 network but is logically divided
into two /24 subnets representing the A and B side respectively like a BSC
where BSC LAN Switches are used. Hence, the subnet mask is 255.255.255.0.
Data transcript for the example configuration:
! Configure Gateway IP addresses;

rrgwc:gw1=192.168.0.1,gw2=192.168.1.1;
! Configure IP addresses for IPS;

rripi:ipaddr=192.168.0.2,ipdevtype=rtipgph,\
ipdevno=0,mask=255.255.255.0,gw=gw1;
rripi:ipaddr=192.168.0.66,ipdevtype=rtippgw,\
rripi:ipaddr=192.168.0.130,ipdevtype=rtippgh,\
7/198 17-APT 210 09 Uen T | 2016-06-03 11

rripi:ipaddr=192.168.0.180,ipdevtype=rtipagw,\
rripi:ipaddr=192.168.0.190,ipdevtype=rtipcth,\
3.4.5 Configure IP Application
Follow the instructions in Reference [21] and associate the IP addresses with
the IPS application. A port shall not be configured for IPS.
! Associate application with IP address;

rrapi:apl=ips,ipaddr=192.168.0.2;
12 7/198 17-APT 210 09 Uen T | 2016-06-03

rrapi:apl=ips,ipaddr=192.168.0.190,ipaddrnum=3;
rrapi:apl=ips,ipaddr=192.168.1.190,ipaddrnum=3;
Note: Optional argument ipaddrnum=n can be used if n sequential

addresses shall be associated with the same application.
3.5 R-PMO, RTT, GMLog, and OEN
3.5.1 IP Addresses
The IP address for R-PMO, RTT, GMLog, and OEN must be within the IP range
of the OM_BSC / Internal_OM subnet. They must all use the same IP address
and shall not be fixed to a specific IP device or interface, that is, the IPDEVNO
and GW parameters of the RRIPI command shall not be used. In this example
configuration, IP address 172.30.38.11 and network mask 255.255.255.240
(the network mask of the OM_BSC / Internal_OM subnet) is used.
3.5.2 Port Parameters

The ports used for R-PMO, RTT, GMLog, and OEN can be chosen arbitrarily but
must not collide with any ports used by other applications (for example Telnet
on port 23) using the same IP address. Furthermore, as a recommendation,
do not use port numbers less than or equal to 1024. The applications must
also be allocated different port numbers. In this example configuration, port
22000 is used for R-PMO, port 23000 for OEN, port 24000 for RTT and port
6000 for GMLog.
When defining port parameters it is possible to set up to four remote IP

addresses (RIP1-RIP4) that are allowed to access the defined port. The
remote IP address shall be the IP address of the host where the accessing IP
application is running (for example an OSS server). If no remote IP address is
defined, access will be granted to any host accessing the port. In this example
configuration, no remote IP address will be set.
It is also possible to configure a DiffServ code point (DSCP) to differentiate the

priority of the IP packets sent over the network. In this example configuration,
no DiffServ code point will be set.
7/198 17-APT 210 09 Uen T | 2016-06-03 13

3.5.3 Event Authorization
R-PMO, RTT, GMLog, and OEN can subscribe to a number of events. The
event subscription must be authorized in the BSC. For a list of event and
application identifiers, see Reference [24]. In this example configuration, all
available events will be authorized.

Follow the instructions in Reference [23] and configure the IP address for
R-PMO, RTT, GMLog, and OEN. For other IP configuration options, see
Reference [3].
! Configure IP address for R-PMO, RTT, GMLog, and OEN;

rripi:ipaddr=172.30.38.11,IPDEVTYPE=RTIPGPH,\
bestbw,mask=255.255.255.240;
3.5.5 Configure IP Application R-PMO

1. IP application R-PMO, that is, associate an IP address with the application.

2. Port parameters for IP application R-PMO.

rrapi:apl=rpm,ipaddr=172.30.38.11;
! Configure port;
rrppi:port=22000,apl=rpm;
3.5.6 Configure IP Application GMLog

1. IP application GMLog, that is, associate an IP address with the application.
2. Port parameters for IP application GMLog.

rrapi:apl=gml,ipaddr=172.30.38.11;
! Configure port;
rrppi:port=6000,apl=gml;
14 7/198 17-APT 210 09 Uen T | 2016-06-03

3.5.7 Configure IP Application OEN

1. IP application OEN, that is, associate an IP address with the application.
2. Port parameters for IP application OEN.

rrapi:apl=oen,ipaddr=172.30.38.11;
! Configure port;
rrppi:port=23000,apl=oen;
3.5.8 Configure IP Application RTT

1. IP application RTT, that is, associate an IP address with the application.
2. Port parameters for IP application RTT.

rrapi:apl=rtt,ipaddr=172.30.38.11;
! Configure port;
rrppi:port=24000,apl=rtt;
3.5.9 Authorize Event Subscriptions
Follow the instructions in Reference [5] and authorize:
1. Application R-PMO to change status of BSC event reporting
2. Application GMLog to change status of BSC event reporting
3. Application OEN to change status of BSC event reporting
4. Application RTT to change status of BSC event reporting
! For R-PMO;
rapmi:aid=0,eid=all;
! For GMLog;
! For OEN;
7/198 17-APT 210 09 Uen T | 2016-06-03 15

! For RTT
3.6 Gb over IP
3.6.1 IP Addresses
The IP addresses for Gb over IP must be within the IP range of the GbIP /
Internal_Gb subnet. There must be one IP address allocated to every RP
that shall support Gb over IP (GPH RP). As a consequence, the IPDEVNO
parameter of the RRIPI command shall be used, but not the GW parameter.
In this example configuration, IP addresses 172.30.12.3 - 172.30.12.4 and
network mask 255.255.255.128 (the network mask of the GbIP / Internal_Gb
subnet) are used for Gb over IP.

The ports used for Gb over IP can be chosen arbitrarily but must not collide
with any existing ports used by other applications using the same IP address.
Furthermore, as a recommendation, do not use port numbers less than or equal
to 1024. In this example configuration, port 45000 is used for Gb over IP.
When defining port parameters it is possible to set up to four remote IP

addresses (RIP1-RIP4) that are allowed to access the defined port. These
parameters are ignored by the Gb over IP application, that is, access will be
granted for all hosts accessing the port even if any specific remote IP address
is defined..
It is also possible to configure a DiffServ code point (DSCP) to differentiate the

priority of the IP packets sent over the network. In this example configuration,
no DiffServ code point will be set.

Follow the instructions in Reference [23] and configure an IP address for Gb
over IP. A fixed IP address, not associated to any gateway, shall be defined.
! Configure IP addresses for Gb over IP;

rripi:ipaddr=172.30.12.3,ipdevtype=RTIPGPH,\
ipdevno=0,mask=255.255.255.128;
ipdevno=1,mask=255.255.255.128;
16 7/198 17-APT 210 09 Uen T | 2016-06-03


1. Port parameters for the Gb over IP application.
2. Associate the Gb over IP application to the defined IP addresses.
! Configure port;
rrppi:port=45000,apl=gbi;
! Associate application with IP addresses;

rrapi:apl=gbi,ipaddr=172.30.12.3;
rrapi:apl=gbi,ipaddr=172.30.12.4;
3.7 Packet Abis over IP
3.7.1 IP Addresses
There are two RP applications that supports Packet Abis over IP. These
are Combined Traffic Handler (CTH), which is only used in Evo Controller
8200/BSC; and Packet Gateway (PGW), which can be used in all other BSC
configurations.
The IP addresses for Packet Abis over IP must be within the IP range of the
AbisIP / Internal_Abis subnet. There must be one IP address allocated to every
RP which shall handle Packet Abis over IP traffic. On top of these one additional
"floating" IP address, which is used for first BSC contact, must be defined. In
the RRIPI command GW parameter shall not be used. IPDEVNO is not used
for the “floating” IP address since it is not statically bound to a specific RP.
If using PGW RP application IPDEVNO parameter shall be used to set IP

address for Abis traffic on a specific PGW RP. If using CTH RP application
the parameter IPDEVNO shall not be used. Instead the APPLSEL argument
shall be used in order to set that the BSC software is responsible of deciding
IP address each CTH RP is to be configured with.
If running CTH RP application one or more CTH RP can be standby. This

means that there are no IP address allocated to these RPs but in the case of
failure of any of the active CTH RPs the IP address and traffic is moved to a
standby RP which becomes active. The number of standby CTH RPs are set
by RALSC command. The number of IP addresses for Abis traffic shall be
equal to the number of CTH RPs minus the number of Standby CTH RPs. If
there are more, some IP addresses will not be used. If there are less, some
CTH-RPs will not handle Packet Abis over IP traffic.
7/198 17-APT 210 09 Uen T | 2016-06-03 17

There is no standby RP concept for the PGW RP application.
Command RALSP can be used to see which RP are handling which Packet
Abis over IP address.

No ports shall be used for Abis over IP application.
Follow the instructions in Reference [23] and configure an IP address for Packet
Abis over IP. An IP address, not associated to any gateway, shall be defined.
! Configure IP addresses for Packet Abis over IP

! on three PGW RPs;
rripi:ipaddr=172.30.74.3,ipdevtype=RTIPPGW,\
ipdevno=0,mask=255.255.255.192;
ipdevno=1,mask=255.255.255.192;
ipdevno=2,mask=255.255.255.192;
! Configure the floating IP address for Packet Abis

! over IP for the PGW RP application;
mask=255.255.255.192;
The same example for Evo Controller 8200/BSC.
Two CTH RPs handle Abis over IP traffic and one CTH RP is standby.
! Configure two IP addresses for

! Packet Abis over IP for CTH RP application;
rripi:ipaddr=172.30.74.3,ipaddrnum=2,ipdevtype=RTIPCTH,\
applsel,mask=255.255.255.192;
! Configure the floating IP address for

! Packet Abis over IP for the CTH RP application;
rripi:ipaddr=172.30.74.6,ipdevtype=RTIPCTH,\
mask=255.255.255.192;
! Set the number of standby CTH RPs to one

ralsc:numsb=1;
18 7/198 17-APT 210 09 Uen T | 2016-06-03

Note: Optional argument ipaddrnum=n can be used if n sequential

addresses shall be associated with the same IP device type

1. Associate the Abis over IP application to the defined IP addresses.
! Associate application with four IP addresses;

rrapi:apl=abi,ipaddr=172.30.74.3;
The same example for Evo Controller 8200/BSC. The difference is that there is
one standby RP without IP address.
! Associate application with three IP addresses;

Note: The same can be done using argument ipaddrnum=n which will
associate n sequential IP addresses to the same IP application.
3.8 A-Interface over IP
3.8.1 IP Addresses
There are two RP application that supports A-interface over IP. These are
Combined Traffic Handler (CTH), which is only used in Evo Controller 8200/BSC
and A-interface Gateway (AGW) which is used in all other BSC configurations.
The IP addresses for A-Interface over IP must be within the IP range of the
A_userplane / Internal_A subnet. There must be one IP address allocated to
each active RP that shall support A-Interface over IP. The IP addresses shall
be reconfigurable addresses, and the application selects which IP device the
IP addresses will be defined for. As a consequence, neither the IPDEVNO
parameter of the RRIPI command, nor the GW parameter shall be used.
Instead the APPLSEL parameter shall be used.
To configure one standby AGW RP then the number of IP addresses shall be

one less than the number of AGW RP. To configure two standby AGW-RP
7/198 17-APT 210 09 Uen T | 2016-06-03 19

then the number of IP addresses shall be two less than the number of AGW
RP, and so on.
For the CTH RP application the number of standby CTH-RPs are set by RALSC
command. The number of IP addresses for A-interface traffic shall be equal to
the number of CTH RPs minus the number of Standby CTH RPs. If there are
more, some IP addresses will not be used. If there are less, some CTH RPs will
not handle A-interface over IP traffic.
Command RALSP can be used to see which RPs are handling which
A-interface IP address.
In this example configuration, IP addresses 172.30.81.3 - 172.30.81.6 and

network mask 255.255.255.240 (the network mask of the A_userplane /
Internal_A subnet) are used for A-Interface over IP.

The A-Interface over IP application in the BSC transmits and receives user
plane data on ports 10 000 - 42 768 for non-multiplexed traffic where even port
numbers are used for RTP and the following odd port number is used for RTCP.
The A-Interface over IP application in the BSC transmits and receives user
plane data on ports 50 000 - 52 048 for multiplexed RTP streams.
Ports are associated with traffic by BSC software. No manual configuration of

port parameters can be done.

Follow the instructions in Reference [23] and configure an IP address for
A-Interface over IP. A fixed IP address, not associated to any gateway, shall be
defined.
! Configure IP addresses for A-Interface over IP;

rripi:ipaddr=172.30.81.3,ipaddrnum=3,ipdevtype=rtipagw,\
mask=255.255.255.240,applsel;
The same example for Evo Controller 8200/BSC. Two CTH RPs handle A over
IP traffic and one CTH RP is standby.
! Configure IP addresses for A-Interface over IP;
rripi:ipaddr=172.30.81.3,ipaddrnum=2,ipdevtype=rtipcth,\
mask=255.255.255.240,applsel;
! Set the number of standby CTH RPs to one

ralsc:numsb=1;
20 7/198 17-APT 210 09 Uen T | 2016-06-03

Note: Optional argument ipaddrnum=n can be used if several addresses in

sequence shall be associated with the same IP device type.

1. Associate the A-Interface over IP application to the defined IP addresses.

rrapi:apl=aip,ipaddr=172.30.81.3;
The same example for Evo Controller 8200/BSC. The difference is that there is
one standby RP without IP address.

Note: The same can be done using argument ipaddrnum=n which will
associate n sequential IP addresses to the same IP application.
3.9 SIGTRAN
3.9.1 IP Addresses, SIGTRAN on RP

The IP address(es) for SIGTRAN must be within the IP range of the SS7 /
Internal_SS7 subnet. There must be one IP address allocated to every RP that
shall support SIGTRAN. IP address and netmask is set by the IHCOI (SIGTRAN
on RP) / IHIFC (SIGTRAN on CP) command. In this example configuration, IP
addresses 172.30.78.2 and 172.30.78.9 and network mask 255.255.255.248
(the network mask of the upper/lower half of the SS7 / Internal_SS7 subnet)
are used for SIGTRAN.
3.9.2 Configure SIGTRAN on RP

1. IP application SIGTRAN, that is, associate an IP address with the

application.
In this set up, the SS7 subnet is a /28 network. Hence, the subnet mask is
255.255.255.240.
7/198 17-APT 210 09 Uen T | 2016-06-03 21

! Configure IP address for SIGTRAN;

ihcoi:ipport=ip-0-2,ipadd=172.30.78.2, \
submask=255.255.255.240;
ihcoi:ipport=ip-1-2,ipadd=172.30.78.9, \
submask=255.255.255.240;
! Define default gateway
ihrdi:ipport=ip-0-2,defgw=172.30.78.1;
ihrdi:ipport=ip-1-2,defgw=172.30.78.8;
! Deblock the ip ports
ihble:ipport=ip-0-2
ihble:ipport=ip-1-2
3.9.3 IP Addresses, SIGTRAN on CP

SIGTRAN on CP can be configured to use one or two internal subnets.
The IP address(es) for SIGTRAN must be within the IP range of the

Internal_SS7 subnets. IP address and netmask is set by the IHIFC command.
In the example configuration with one internal subnet in Section 3.9.4 on
page 22, IP addresses 172.30.78.2 and 172.30.78.9 and network mask
255.255.255.240 is used for SIGTRAN.
In the example configuration with two internal subnets in Section 3.9.5 on

page 23, IP addresses 172.30.78.2 and 172.30.78.9 and network mask
255.255.255.248 is used for SIGTRAN.
Note: SIGTRAN on CP is only applicable for Evo Controller 8200/BSC.
3.9.4 Configure SIGTRAN on CP, One Internal Subnet
Follow the instruction in Reference [18] and configure:

application.
In this set up, the SS7 subnet is a /28 network. Hence, the subnet mask is
255.255.255.240.
The VLAN tag used is 51.
On top of the IP addresses for the Sigtran end-points and default gateway,
there is an additional set of two addresses (PINGA and PINGB below) for
router supervision.
! Configure Virtual Ethernet Interfaces:

IHIFI:VIF=ETHA-51
IHIFI:VIF=ETHB-51;
22 7/198 17-APT 210 09 Uen T | 2016-06-03

IHIFC:VIF=ETHA-51, ADD, IP=172.30.78.2, \

NETMASK=255.255.255.240, ARP=YES;
IHIFC:VIF=ETHB-51, ADD, IP=172.30.78.9, \
NETMASK=255.255.255.240, ARP=YES;
!Router Path Supervision (RPS)!
IHRSI:VIFP=ETH-51, GW=172.30.78.1&172.30.78.8, \
PINGA=172.30.78.6, PINGB=172.30.78.14,IPMIGR=YES;
IHRSP:VIFP=ETH-51;
IHRHC:ADD, VIF=ETHA-51, DEFGW=172.30.78.1, \
PREF=2;
IHRHC:ADD, VIF=ETHB-51, DEFGW=172.30.78.8, \
PREF=1;
! Create SCTP End Point

IHBII:LIP="172.30.78.2"&"172.30.78.9",\
EPID=<MSC EPID>,USER=M3UA,MODE=CLIENT,\
SCTPCP, LPN=33144;
! Create SCTP Association

IHADI:SAID=<MSC SAID>,EPID=<MSC EPID>,\
RIP="<MSC IP ADDRESS 1>"&"<MSC IP ADDRESS 2>",SCTPCP;
IHAPC:SAID=<MSC SAID>,PLIP="172.30.78.2",\
PRIP="<MSC IP ADDRESS 1";
! Set up and activate M3UA Routing

M3RSI:DEST=<DEST>,SAID=<MSC SAID>,\
PRIO=1,BMODE=PEER;
M3RAI:DEST=<DEST>,SAID=<MSC SAID>;
! Establish and activate SCTP association

IHASC:SAID=<MSC SAID>,PROC=ESTB,USER=M3UA,SCTPCP;
M3ASC:SAID=<MSC SAID>,PROC=ACT;
IHCLP:EPID=ALL,SAID=ALL;
M3RSP:DEST=ALL;
C7SPP:SP=ALL;
Note: SIGTRAN on CP operates in client mode on the BSC.
3.9.5 Configure SIGTRAN on CP, Two Internal Subnets

Follow the instruction in Reference [18] and configure:

application.
7/198 17-APT 210 09 Uen T | 2016-06-03 23

In this set up, the SS7 subnets are two /29 networks. Hence, the subnet mask
is 255.255.255.248.
The VLAN tags used are 51 and 52.
! Configure Virtual Ethernet Interfaces:

IHIFI:VIF=ETHA-51
IHIFI:VIF=ETHB-52;
IHIFC:VIF=ETHA-51, ADD, IP=172.30.78.2, \
NETMASK=255.255.255.248, ARP=YES;
IHIFC:VIF=ETHB-52, ADD, IP=172.30.78.9, \
NETMASK=255.255.255.248, ARP=YES;
IHRHC:ADD, VIF=ETHA-51, DEFGW=172.30.78.1;
IHRHC:ADD, VIF=ETHB-52, DEFGW=172.30.78.8;
! Create SCTP End Point

IHBII:LIP="172.30.78.2"&"172.30.78.9",\
EPID=<MSC EPID>,USER=M3UA,MODE=CLIENT,\
SCTPCP, LPN=33144;
! Create SCTP Association

IHADI:SAID=<MSC SAID>,EPID=<MSC EPID>,\
RIP="<MSC IP ADDRESS 1>"&"<MSC IP ADDRESS 2>",SCTPCP \
RPN=<RPN>;
IHAPC:SAID=<MSC SAID>,PLIP="172.30.78.2",\
PRIP="<MSC IP ADDRESS 1";
! Set up and activate M3UA Routing

M3RSI:DEST=<DEST>,SAID=<MSC SAID>,\
PRIO=1,BMODE=PEER;
M3RAI:DEST=<DEST>,SAID=<MSC SAID>;
! Establish and activate SCTP association

IHASC:SAID=<MSC SAID>,PROC=ESTB,USER=M3UA,SCTPCP;
M3ASC:SAID=<MSC SAID>,PROC=ACT;
IHCLP:EPID=ALL,SAID=ALL;
M3RSP:DEST=ALL;
C7SPP:SP=ALL;
Note: SIGTRAN on CP operates in client mode on the BSC.
24 7/198 17-APT 210 09 Uen T | 2016-06-03

3.10 SMS CBC
3.10.1 IP Addresses
The IP addresses for the SMS CBC must be within the IP range of the CBC
/ Internal_CBC subnet. There must be one IP address allocated to the SMS
CBC application. If dedication mode B is used then both the IPDEVNO and
IPDEV2NO parameters of the RRIPI command shall be used, but not the GW
parameter. If dedication mode A is used the IPDEV2NO parameter is not used.
See Reference [2] for more information on dedication mode A and dedication
mode B.
In this example configuration IP address 172.30.90.3 and network mask

255.255.255.248 (the network mask of the CBC / Internal_CBC subnet) are
used for SMS CBC application.

The port 48049 is to be used for the SMS CBC application.

Follow the instructions in Reference [23] and configure an IP address for SMS
CBC. A semi-fixed IP address, not associated to any gateway, shall be defined.
! Configure IP addresses for SMS CBC;

! Dedication mode B;
ipdevno=0,ipdev2no=1,mask=255.255.255.248;
1. Port parameter for the SMS CBC application.
2. Associate the SMS CBC application to the defined IP address.
! Configure port;
rrppi:port=48049,apl=cbs;

rrapi:apl=cbs,ipaddr=172.30.90.3;
7/198 17-APT 210 09 Uen T | 2016-06-03 25

3.11 Network Time Protocol on SCX
3.11.1 IP Addresses
The IP addresses for Network Time Protocol (NTP) service on SCX must be
within the IP range of the Internal_OM subnet.
Note: NTP on SCX is only applicable for Evo Controller 8200/BSC.
3.11.2 Configure NTP on SCX

The AXE commands to configure NTP on SCX are found in Reference [25].
Adding and removing external time references requires changes to the Access
Control Lists (ACLs) in the NWI-E.
Note that the configuration of the NTP service on SCX is done through AP
commands, not via MML commands. In this example we use the fake external
time references 256.3.4.1, 256.3.4.2, and 256.3.4.3. Note that these are invalid
IP addresses.
timerefscxconf -i -s 0 -a 172.30.38.12 \
-b 255.255.255.240 -d 172.30.38.1
timerefscxconf -i -s 25 -a 172.30.38.13 \
-b 255.255.255.240 -d 172.30.38.2
timerefadd -i 256.3.4.1 -n PrimaryServer

timerefadd -i 256.3.4.2 -n SecondaryServer
timerefadd -i 256.3.4.3 -n TertiaryServer
timerefstart -s NTP
To allow traffic between the NTP service and external time references to pass
through the NWI-E the ACLs in the NWI-E have to be updated as well. This
is done either by logging into the NWI-Es and manually add the ACLs; or
use OSS to modify the configuration. Note that this must be done for both
NWI-E since they do not have their configurations synchronized between them.
Commands for NWI-E are described in detail in Reference [13], Reference
[14] and Reference [15].
Both NWI-E boards must be configured with ACLs according to standard

configuration. Use the following command to verify whether ACLs are installed
or not:
show access-list any
26 7/198 17-APT 210 09 Uen T | 2016-06-03

If the printout is empty, the NWI-E boards should be reconfigured using the
script in Reference [11] in combination with the template in Reference [12].
Note that the parameter ACLs needs to be set to yes. If a new configuration is
installed using the correct parameter file template, then no further actions need
to be performed. If an old configuration with ACLs is already in place, then add
the new rules for SCX according to below.
Definition of ACLs that allow traffic through for the first external time reference
and the first NTP service IP address:
create access-list SCX_ntpserver_1_1_in "protocol udp ; \

destination-address 172.30.38.12/32 ; \
source-address 256.3.4.1/32 ; \
source-port 123" "permit" application "Cli"
configure access-list add SCX_ntpserver_1_1_in after \

SNTP_1_out any application "Cli" ingress
create access-list SCX_ntpserver_1_1_out "protocol udp ; \

destination-address 256.3.4.1/32 ; \
source-address 172.30.38.12/32 ; \
source-port 123" "permit" application "Cli"
configure access-list add SCX_ntpserver_1_1_out after \

SCX_ntpserver_1_1_in any application "Cli" ingress
Similar ACLs are created for the second and third external time reference; and
for the second IP address of the NTP service.
Additional ACLs are then needed to block all other traffic to and from the
IP address of the NTP service. These are added after the ACLs that allow
the traffic through. The example below shows the ACLs for the IP address of
the first NTP service.
create access-list denyfromSCXclient_1 "source-address \

172.30.38.12/32" "deny" application "Cli"
configure access-list add denyfromSCXclient_1 after \

SCX_ntpserver_1_<y>_out any application "Cli" ingress
create access-list denytoSCXclient_1 "destination-address \

172.30.38.12/32" "deny" application "Cli"
configure access-list add denytoSCXclient_1 after \

denyfromSCXclient_1 any application "Cli" ingress
Note: If no ACL called SNTP_<x>_in and SNTP_<x>_out are defined in the

NWI-E then place the first ACL after the ACL called vrrp_acl.
7/198 17-APT 210 09 Uen T | 2016-06-03 27

When an external time reference is no longer used it is best to remove the

ACL for it from the NWI-E configuration. Perform the following configuration
for all SCX specific ACLs on each NWI-E, where <ACL name> is the name
of the ACL that allows traffic through for a specific external time reference.
In the example above the names are SCX_ntpserver_1_1_in and
SCX_ntpserver_1_1_out.
configure access-list delete <ACL name> any

delete access-list <ACL name>
From the perspective of NWI-E changing the IP address of an external time

reference is a matter of combining removal of the ACL for the old IP address
and adding a new ACL for the new IP address.
As a last action, regardless of whether you have removed ACLs or added

ACLs, save the configuration:
save configuration
28 7/198 17-APT 210 09 Uen T | 2016-06-03

IP Consistency Check
4 IP Consistency Check
4.1 Verify IP Connectivity to the BSC IP Infrastructure

Prior to the final step of checking the consistency of the configuration, verify the
IP connectivity from the OSS servers to the BSC using the PING command.
Ping the IP addresses of the BSC IP network interfaces on the OM_BSC /
Internal_OM subnet using a shell window in OSS.
ping 172.30.38.1
172.30.38.1 is alive
ping 172.30.38.2
172.30.38.2 is alive
If no answer is received, make sure that the prerequisites 1 and 2 in Section 2

on page 5 are fulfilled.
4.2 IP Configuration Consistency Check

As the final step, perform the actions described in Reference [8] to verify the
consistency of the BSC IP configuration.
7/198 17-APT 210 09 Uen T | 2016-06-03 29

30 7/198 17-APT 210 09 Uen T | 2016-06-03

Concepts
5 Concepts
AGW RP Regional Processor with AGW application.
BSC IP Network Interfaces

The part of the BSC that provides IP connectivity to
the different IP hosts within the BSC. It is implemented
either by the BSC LAN switches or by the BSC NWI-E.
BSC LAN Switches

A hardware implementation of the BSC IP network
interfaces. It consists of two Summit 48si L2/L3
switches from Extreme Networks.
BSC NWI-E A hardware implementation of the BSC IP network

interfaces. It consists of two single slot GEM/EGEM
boards, which can handle both Layer 2 and Layer 3.
CTH RP Regional Processor with CTH application.
Floating IP Address
An IP address used by the PGW application but not
bound to any specific RP board. It is recommended to
let all the STN nodes connect to this address as the
PGW application will redirect the communication to the
PGW RP with least load.
GPH RP Regional Processor with GPH application.
IP Gateway Supervision
IP Gateway Supervision (IPS) is the functionality in
the GPRS Packet Handler (GPH) that detects when
the connection between an IP device and a BSC LAN
switch is lost. In the case of a connection failure an
alarm will be raised, see Reference [22].
IP Application An IP application in this context is an application that

uses the services of BSC IP Connectivity and can be
associated with an IP address. The IP applications are
R-PMO, GMLog, IPS, OEN, SIGTRAN, Gb over IP and
Abis over IP.
IP Device An IP device is a device that IP parameters (for example

IP address) can be assigned to. For GPH the device
owning block is RTIPGPH and the IP devices are
named as RTIPGPH-<no>. For PGW the device owning
block is RTIPPGW and the IP devices are named
RTIPPGW-<no>
7/198 17-APT 210 09 Uen T | 2016-06-03 31

PGW RP Regional Processor with PGW application.
SLI Regional Processor with SIGTRAN application.
SMS CBC SMS Cell Broadcast Center, an application providing

a interface to external CBC servers for SMS cell
broadcasts.
32 7/198 17-APT 210 09 Uen T | 2016-06-03

Glossary
Glossary
ABI IPS
Abis over IP (application name) IP Gateway Supervision
ACLs L2
Access Control Lists Layer 2 (Ethernet)
AGW L3
A-interface Gateway Layer 3 (IP)
BSC LAN
Base Station Controller Local Area Network
BTS MGW
Base Transceiver Station Media Gateway
CLI NTP
Command Line Interface Network Time Protocol
CN NWI-E
Core Network Network Interface - Ethernet
CTH O&M
Combined Traffic Handler Operation and Maintenance
DiffServ OEN
Differentiated Services Open Event Notification Interface
DSCP OSS
DiffServ code point Operation and Support System
GBI PGW
Gb over IP (application name) Packet Gateway
GMLog R-PMO
GPRS Mobile Logging Real-Time Performance Monitoring
GPH RP
GPRS Packet Handler Regional Processor
GPRS RTT
General Packet Radio Service Real Time Trace
ICMP SGSN
Internet Control Message Protocol Serving GPRS Support Node
IP SIGTRAN
Internet Protocol Signalling Transport
7/198 17-APT 210 09 Uen T | 2016-06-03 33

SLI
Sigtran Link Interface
SMS CBC
Short Message Service Cell Broadcast Center
SS7
Signalling System #7
STN
Site Transport Node
TCP
Transmission Control Protocol
UDP
User Datagram Protocol
VLAN
Virtual LAN
34 7/198 17-APT 210 09 Uen T | 2016-06-03

Reference List
Reference List
Ericsson Documents
[1] Block Group GPRS Gb Interface in the PCU (BG-GBPCU)
[2] BSC, Dedicated RP Resources for CBS, Change
[3] BSC, Dedicated RP Resources for Event Handling, Change
[4] BSC Event Reporting, 30/155 17-APT 210 09
[5] BSC, Event Reporting, Performance Monitoring Subscription Status,

Change
[6] BSC IP Addressing
[7] BSC IP Connectivity, 3/155 17-CRT 242 12 Uen
[8] BSC, IP Connectivity Consistency Check, Perform
[9] BSC LAN Switch Configuration
[10] BSC NWI-E Configuration
[11] BSC NWI-E Configuration File Compiler
[12] BSC NWI-E Parameter File Template
[13] ExtremeXOS 16.1 User Guide
[14] ExtremeXOS Command Rererence Guide for Release 16.1
[15] ExtremeXOS Quick Guide
[16] GPRS, Gb over IP, 4/155 17-CRT 242 12 Uen
[17] IP Port, Connect
[18] IP Transport, Maintenance and Operation, Set
[19] Packet Based and Bandwidth Optimized Abis, 42/155 17-APT 210 09 Uen
[20] RADIO OPERATION AND MAINTENANCE SUBSYSTEM (ROS)
[21] Radio Transmission, IP Applications Configuration, Change
[22] RADIO TRANSMISSION IP GATEWAY FAULT
[23] Radio Transmission, IP Services Configuration, Change
7/198 17-APT 210 09 Uen T | 2016-06-03 35

[24] ROS, RP Application Support and Event Handling Changeable Exchange

Adaptation
[25] SCX Based UTC Reference Clock, Connect
36 7/198 17-APT 210 09 Uen T | 2016-06-03

BSC IP Application Set Up: User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSC IP Application Set Up: User Guide

Uploaded by

Copyright:

Available Formats

BSC IP Application Set Up

7/198 17-APT 210 09 Uen T

Ericsson is the trademark or registered trademark of

7/198 17-APT 210 09 Uen T | 2016-06-03

3 Principles and Example Configurations 7

7/198 17-APT 210 09 Uen T | 2016-06-03

7/198 17-APT 210 09 Uen T | 2016-06-03

• Packet Abis over IP

• SIGTRAN (SS7 over IP)

• GPRS Mobile Logging (GMLog)

• BSC Internal IP Gateway Supervision (IPS)

• Open Event Notification Interface (OEN)

• Real-Time Performance Monitoring (R-PMO)

• Real Time Trace (RTT)

• Short Message Service Cell Broadcast Center (SMS CBC)

• Network Time Protocol (NTP) for Evo Controller 8200/BSC

The reader of this document is expected to be familiar with the BSC IP

For further information relating to recommended IP addressing schemes, see

1.2 Revision Information

The changes introduced in revision L (G11B) are the following:

• A clarification is added that IPDEVNO is not used for the “floating” IP

7/198 17-APT 210 09 Uen T | 2016-06-03 1

• SMS CBC is added.

The change introduced in revision M (G12B) is the following:

• Updates for Evo Controller 8200.

The changes introduced in revision M1 (G12B) are the following:

• Restructured document to make it easier to use for specific IP applications.

• Introduced NTP on SCX.

The change introduced in revision M2 (G12B) is the following;

• Correct minor link errors in the reference list.

The changes introduced in revision N1 (G13B) are the following;

• Added RP application Combined Traffic Handler.

• Correct minor link errors in the reference list.

• BSC shall be set as “client” when using Sigtran on CP.

The change introduced in revision N2 (G13B) is the following;

• Updated example for Evo Controller 8200 in chapter Section 3.8.3 on

The change introduced in revision N3 (G13B) is the following;

• Corrected example for Evo Controller 8200 in chapters Section 3.7.3 on

The changes introduced in revision N4 (G13B) are the following:

• Removed Mobile@Home information

• Added information regarding separate subnets for Sigtran on CP

The change introduced in revision N5 (G14B) is the following:

• Updated references for XOS 16.1

The change introduced in revision T (G15B) is the following:

• Updated due to administrative reasons

1.3 Typographic Conventions

2 7/198 17-APT 210 09 Uen T | 2016-06-03

System response is formatted as:

7/198 17-APT 210 09 Uen T | 2016-06-03 3

4 7/198 17-APT 210 09 Uen T | 2016-06-03

1. The BSC IP Infrastructure must be configured as described in Reference

2. The BSC IP Infrastructure must have functioning IP connectivity to the OSS.

3. If Gb over IP is installed, the BSC IP Infrastructure must have functioning

4. If Packet Abis over IP is installed, the BSC IP Infrastructure must have

5. If A-Interface over IP is installed, the BSC IP Infrastructure must have

6. If SIGTRAN is installed, the BSC IP Infrastructure must have functioning

7. If SMS CBC is installed, the BSC IP Infrastructure must have functioning

7/198 17-APT 210 09 Uen T | 2016-06-03 5

6 7/198 17-APT 210 09 Uen T | 2016-06-03

3 Principles and Example Configurations

3.2 Subnet and VLAN Structure

Note: IP subnet addresses and sizes are fully configurable.

7/198 17-APT 210 09 Uen T | 2016-06-03 7