BSC IP Addressing [PDF]

Zitiervorschau

BSC IP Addressing USER GUIDE

9/198 17-APT 210 09 Uen AB

Copyright © Ericsson AB 2005-2012, 2014, 2016-2019. 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.

9/198 17-APT 210 09 Uen AB | 2019-03-29

Contents

Contents 1

Introduction

1

1.1

Overview

1

1.2

Revision Information

1

2

Configuration

3

2.1

BSC and Connecting Networks

3

2.2

IP Addressing

5

2.3

Migration to BSC IP Connectivity

17

3

Concepts

19

Glossary

21

Reference List

23

9/198 17-APT 210 09 Uen AB | 2019-03-29

BSC IP Addressing

9/198 17-APT 210 09 Uen AB | 2019-03-29

Introduction

1

Introduction

1.1

Overview This document provides an overview of IP addressing for BSC IP Connectivity. It serves as information to network and security engineers to deepen their understanding of the BSC IP infrastructure, facilitating the design of operator-specific IP address plans and IP access control. This User Guide briefly describes the BSC IP Connectivity and BSC IP communication with other nodes. The requirements on each of the subnets, from an IP addressing point of view, are presented as well as an IP host allocation scheme. The reader is assumed to be familiar with IP networking.

1.2

Revision Information

1.2.1

Changes Introduced in Revision AA — Removed reference to AGP43.

1.2.2

Changes Introduced in Revision Z — Removed references for LAN Switch Summit48i.

1.2.3

Changes Introduced in Revision Y — Added reference to “Evo Controller 8200/BSC and EvoC 8230 Hardware Dimensioning Handbook”.

1.2.4

Changes Introduced in Revision X — Introduction of SMX-based BSC, EvoC 8230. — Updated XOS references due to XOS 16.2.

1.2.5

Changes Introduced in Revision V — Updated XOS references due to XOS 16.1.

9/198 17-APT 210 09 Uen AB | 2019-03-29

1

BSC IP Addressing

1.2.6

Changes Introduced in Revision S — Removed Mobile@Home references. — Updated references to documentation for APG4x. — Removed support for APG40.

2

9/198 17-APT 210 09 Uen AB | 2019-03-29

Configuration

2

Configuration

2.1

BSC and Connecting Networks Figure 1, depicts the IP terminating network elements in the BSC: — BSC IP network interfaces — Backbone Network — The Serving SGSN — The STN or Baseband Radio Node on BTS side — SS7 Signaling Nodes (for instance, MSC, SMLC) — OSS — MGW — CBC IP traffic is terminated in the BSC in the RP, APG43L, and the STOC. The applications executing on these IP hosts communicate with other nodes, such as the SGSN, STN, SS7 nodes, MGW, and OSS. BSC IP Connectivity provides the necessary IP infrastructure in the BSC for traffic separation and management of IP traffic to and from the BSC. It consists of two L2/L3 switches and the configuration of these switches. There are two implementations of the BSC IP network interfaces. The first implementation is the BSC NWI-E 450A, a GEM/EGEM/EGEM2-board based on a redesigned Summit X450a from Extreme Networks. The BSC NWI-E 450A is later referred to as NWI-E. The third implementation is the SMX, an Ericsson developed product integrated in the EGEM2 infrastructure. See Reference [4] for details on the configuration of the BSC NWI-E, Reference [7] for details on the configuration of SMX-based BSC, and Reference [2] for more information regarding the setup of BSC IP enabled applications. The IP infrastructure outside the BSC is not within the scope of this User Guide, but it is assumed to include some key components: — A resilient site LAN to which all IP enabled nodes on a site are connected. — Site routers, providing routing and IP connectivity to networks external to the site. — A backbone network to which all sites (that is, all site routers) are connected. The details of this infrastructure are operator-specific and are beyond the scope of this User Guide.

9/198 17-APT 210 09 Uen AB | 2019-03-29

3

BSC IP Addressing

MGW

SS7 nodes (MSC, ..)

OSS

STN (BTS)

SGSN

CBC server

IP Backbone

Site Routers

Site LAN CBC subnet

BSC

BSC IP network interfaces SS7 subnet GbIP subnet

AbisIP subnet

A_userplane subnet OM_BSC subnet

RP GBI

Figure 1

ABI

AIP

CBS

RPMO GMLOG OEN

RP APG43

STOC

RP NTP

SLI SIGTRAN

Essential IP Subnets and Communication Paths There are several types of IP traffic terminated in the BSC: — GPRS traffic over the Gb interface — Packet Abis over IP traffic — SS7 traffic over SS7 network — OAM traffic — A-Interface over IP traffic

4

9/198 17-APT 210 09 Uen AB | 2019-03-29

Configuration

— SMSCB traffic This is shown in Figure 1. The thick arrow headed paths represent routing paths that use the IP network through the BSC IP network interfaces, through the Site Routers, and over the IP Backbone. These traffic types are separated into several networks, denoted in this User Guide as the GbIP, AbisIP, SS7, A_userplane, CBC, and OAM networks. For a description of the BSC IP Infrastructure, see Reference [10].

2.2

IP Addressing

2.2.1

VLANs and IP Routers The VLANs configured in the BSC NWI-E using network type 1 are shown in Figure 2 for HD nodes and Evo Controller 8100 and in Figure 3 for Evo Controller 8200 nodes.

AoIP net SS7 net CBC net Abis net Gb net O&M net

SR_SS7

SR_CBC SR_Abis SR_Gb

VRRP SR_OM VRRP SR_Gb VRRP SR_Abis VRRP SR_CBC VRRP SR_SS7 VRRP SR_A_userplane

SR_OM

SR_OM SR_Gb

SR_Abis

SR_CBC

SR_A_userplane

SR_A_userplane

Intercon

Intercon

VRRP BSC_Inner

BSC_Inner

BSC_Inner LH_B

LH_A

A-side BSC NWI-E

B-side BSC NWI-E

STOC/ NTP GARP

Figure 2

SR_SS7

(A side)

APG43

STOC/ NTP

RP magazine (AXE)

(B side)

GARP

BSC NWI-E VLANs for a Network of Type 1

9/198 17-APT 210 09 Uen AB | 2019-03-29

5

BSC IP Addressing

AoIP net SS7 net CBC net Abis net Gb net O&M net

SR_SS7

SR_CBC SR_Abis SR_Gb

VRRP SR_OM VRRP SR_Gb VRRP SR_Abis VRRP SR_CBC VRRP SR_SS7 VRRP SR_A_userplane

SR_OM

SR_Abis

SR_OM SR_Gb

SR_SS7

SR_CBC

SR_A_userplane

SR_A_userplane

Intercon

Intercon

VRRP BSC_Inner

BSC_Inner SS7_Inner

BSC_Inner

SS7_Inner

LH_B

LH_A

A-side BSC NWI-E

B-side BSC NWI-E

APG43

RP magazine (AXE)

(A side)

Figure 3

(B side)

BSC NWI-E VLANs for a Network of Type 1 on Evo Controller 8200

V R R P _ S R A u se rp la n e V R R P _ S R A b is VRRP_SRG B VRRP_SRCBC VRRP_SRO M SR_CBC

SR_O M

SR_SS7

SR_G B

S R _ A b is

S R _ A _ u se rp la n e

S R _ A _ u se rp la n e

SR_G B

S R _ A b is

SR_CBC

SR_O M SR_SS7

V R _S S 7

V R _S S 7

VR_O M

V R _C B C

VR_G B

V R _A _u serplane

V R _A bis

V R _A _u serplane A _ u se rp la n e _ In n e r

V R _A bis

VR_G B

V R _C B C

VR_O M

A _ u se rp la n e _ In n e r A b is_ In n e r

A b is_ In n e r G B _ In n e r

G B _ In n e r

C B C _ In n e r

C B C _ In n e r

S S 7 _ in n e r O E N _ In n e r IP S _ In n e r

IP S _ In n e r O M _ In n e r

T IP C E V O E T _ In g re ss

S S 7 _ in n e r

O E N _ In n e r V R R P _ O M In n e r

O M _ In n e r DRBD

T IP C

DRBD

APZ_B/ LH_B

APZ_A/ LH_A

S M X S id e B

S M X S id e A

A P G 43L M ixed

Figure 4

6

E V O E T _ In g re ss

1G B ack plane 10G B ack plane

BSC SMX VLANs and Virtual Routers for External Network Type 3 on SMX-based BSC

9/198 17-APT 210 09 Uen AB | 2019-03-29

Configuration

In the configuration of the BSC NWI-E, there is a one-to-many relation between a VLAN and IP subnets. In the configuration of the BSC SMX, there is one-to-one relation between VLAN and IP subnet. Listed below are descriptions of the subnets and their minimum size. Note:

The term public address, as used in this context, means a non-reusable IP address within the operator network plan. Such an address is either a public or private address, as defined by RFC 1597 (see Reference [12]) at the discretion of the operator. Furthermore, several protocols used by the BSC do not support Network Address Translation (NAT).

— OM_BSC / Internal_OM: A public subnet to access the Real-Time Performance Monitoring (R-PMO), GPRS/EGPRS Mobile Logging (GMLOG), Real Time Trace (RTT), Time-of-Day (NTP) on a dedicated GARP-2 for the BSC, and the Remote Operation and Maintenance Terminal (OMT) over IP application on the STOC, and APG43L. Currently, a maximum of eight IP addresses are needed and as a consequence, a /28 subnet is sufficient. See Section 2.2.2 on page 10 for a proposed host numbering scheme. On the NWI-E, this subnet is one of many subnets in VLAN BSC_Inner. On the SMX, this subnet belongs to VLAN OM_Inner. — OEN_BSC / Internal_OEN: A public subnet to access Open Event Notification Interface (OEN) applications on the RP. Currently, a maximum of three IP addresses are needed and as a consequence, a /29 subnet is sufficient. See Section 2.2.2 on page 10 for a proposed host numbering scheme. On the NWI-E, this subnet is one of many subnets in VLAN BSC_Inner. On the SMX, this subnet belongs to VLAN OEN_Inner. — IPS / Internal_IPS: Private subnet with two IP addresses allocated per RP connected with Ethernet backplane and one IP address for each of the two BSC IP network interfaces. To keep it simple the same subnet or subnets can be reused in all BSCs. For NWI-E and SMX a single /23 subnet can be used. This spans both planes. The same subnet masks must be used both in the BSC IP network interfaces and in the configuration of the IP Gateway Supervision in the BSC. See Section 2.2.2 on page 10 for a proposed host numbering scheme. On the NWI-E, this subnet is one of many subnets in VLAN BSC_Inner. On the SMX, this subnet belongs to VLAN IPS_Inner. — GbIP / Internal_Gb: A public subnet with one IP address per GPH RP running Gb over IP and one IP address for each of the two BSC IP network interfaces. Allocate a subnet sufficiently large to cover the largest BSC configuration expected. See Reference [8] and Reference [9] for needed amount of GPH RPs. On the NWI-E, this subnet is one of many subnets in VLAN BSC_Inner. On SMX, this subnet belongs to VLAN Gb_Inner. — AbisIP / Internal_Abis: A public subnet with one IP address per PGW or CTH RP running Packet Abis over IP, one additional "floating" IP address, see Reference [2], and one IP address for each of the two BSC IP network interfaces. Allocate a subnet sufficiently large to cover the largest BSC

9/198 17-APT 210 09 Uen AB | 2019-03-29

7

BSC IP Addressing

configuration expected. See Reference [8] for needed amount of PGW RPs and Reference [9] for needed amount of CTH RPs. On the NWI-E, this subnet is one of many subnets in VLAN BSC_Inner. On SMX this subnet belongs to VLAN Abis_Inner. — A_userplane / Internal_A: A public subnet with one IP address per AGW or CTH RP running A-Interface over IP and one IP address for each of the two BSC IP network interfaces. Allocate a subnet sufficiently large to cover the largest BSC configuration expected. See Reference [8] for needed amount of AGW RPs and Reference [9] for needed amount of CTH RPs. On the NWI-E, this subnet is one of many subnets in VLAN BSC_Inner. On SMX, this subnet is used in VLAN A_userplane_Inner. — SS7 / Internal_SS7: A public subnet with one IP address per SIGTRAN RP running SS7 and optionally one IP address for each of the two BSC IP network interfaces. On the NWI-E, for all nodes, except Evo Controller 8200 this subnet is one of many subnets in VLAN BSC_Inner. On Evo Controller 8200 (with NW-IE) and Evo Controller 8230 (with SMX) this subnet belongs to VLAN SS7_Inner. — CBC / Internal_CBC: A public subnet with one IP address for the SMS CBC application and two IP addresses for the BSC IP network interfaces. On the NWI-E, this subnet is one of many subnets in the VLAN BSC_Inner. On SMX this subnet belongs to VLAN CBC_Inner. — LH_A and LH_B: Not subnets in themselves, but VLANs used for inter-RP communication. No IP subnet allocated since the inter-RP traffic is using a MAC-addressing protocol only. The identification and separation of the traffic in the BSC IP network interfaces is done by looking at the protocol number being transported by Ethernet, hence these VLANs are protocol-based VLANs, not subnet-based. LH_A and LH_B VLANs are not used in SMX configuration. — Intercon / Internal_Intercon: Used for interconnection and routing between the two BSC IP network interfaces. To simplify configuration, allocate a private IP subnet and reuse it on all BSC IP network interfaces. See Section 2.2.2 on page 10 for a proposed host numbering scheme. This subnet is not used in SMX configuration. — SR_Gb: Subnet toward the site routers for SGSN traffic. The BSC IP network interfaces require two IP addresses. One extra IP address can be needed if VRRP is used. There are no additional requirements on subnet size, as this is site-dependent. — SR_Abis: Subnet toward the site routers for STN and Baseband Radio traffic. The BSC IP network interfaces require two IP addresses. One extra IP address can be needed if VRRP is used. There are no additional requirements on subnet size, as this is site-dependent. — SR_OM: Subnet toward the site routers for OAM traffic. The BSC IP network interfaces require two IP addresses. One extra IP address can be needed if VRRP is used. There are no additional requirements on subnet size, as this is site-dependent.

8

9/198 17-APT 210 09 Uen AB | 2019-03-29

Configuration

— SR_SS7: Subnet toward the site routers for SIGTRAN traffic. The BSC IP network interfaces require two IP addresses. On the NWI-E, a third IP address is assumed for VRRP. However, it is still recommended to avoid using the VRRP address for routing to since other resiliency mechanisms exist for SIGTRAN. There are no additional requirements on subnet size, as this is site-dependent. — SR_CBC: Subnet toward the site routers for SMS CBC traffic. The BSC IP network interfaces require two IP addresses. One extra IP address can be required if VRRP is used. There are no additional requirements on subnet size, as this is site-dependent. To simplify the routing setup and subnet allocation, it is recommended that the respective subnets are allocated from sufficiently large supernets. The OM_BSC supernet can be divided into equally large OM_BSC subnets per BSC and the same is done for the other supernets. As an example: the supernet 172.30.38.0/24 is allocated to OM_BSC of all BSCs on a particular site. The first BSC is allocated the 172.30.38.0/28 subnet for OM_BSC, the next BSC is allocated the 172.30.38.16/28 subnet for OM_BSC, and so on, to a maximum of 16 BSCs. See Reference [13] for more information regarding subnets and supernets. The configuration of the subnets listed above is obligatory under the conditions shown in Table 1: Table 1

BSC IP Connectivity subnets

Subnet

Condition

OM_BSC / Internal_OM, SR_OM

Mandatory

IPS / Internal_IPS

Mandatory

Intercon / Internal_Intercon

For NWI-E the existence of depends on which network type that is used, see Reference [4]. Not used in SMX configuration

GbIP / Internal_Gb, SR_Gb

Only if Gb over IP is used

AbisIP / Internal_Abis, SR_Abis

Only if Packet Abis over IP is used

SS7 / Internal_SS7, SR_SS7

Only if SIGTRAN is used

A_userplane / Internal_A, SR_A_userplane

Only if A-Interface over IP is used

CBC / Internal_CBC, SR_CBC

Only if SMS CBC is used

LH_A, LH_B

Mandatory for NWI-E. Not used in SMX configuration.

9/198 17-APT 210 09 Uen AB | 2019-03-29

9

BSC IP Addressing

2.2.2

Hosts and Gateways For the subnets discussed in Section 2.2.1 on page 5, allocation of host addresses can be done freely. However, this chapter proposes a host address allocation scheme when using external network type 1 that is supported by the BSC NWI-E. See Reference [4] for more information about the different external network types. It is strongly recommended that the same external network type and scheme, whether it be the proposed or a proprietary scheme, is applied to all BSC installations to simplify configuration and support. Table 2

Host Address Allocation in Subnet OM_BSC

Host Function 0 Network number 1 A-side switch 2 B-side switch 3 APG43L, A side 4 APG43L, B side 5 APG43L, cluster address 6 Not allocated 7 Not allocated 8 Not allocated 9 Not allocated 10 Not allocated 11 R-PMO/GMLOG/RTT/OEN RP 12 STOC; first RP dedicated to Time-of-Day (NTP); SCXB A/SMXB A NTP 13 STOC; second RP dedicated to Time-of-Day (NTP); SCXB B/SMXB B NTP 14 Gateway address (If three address VRRP configuration is used) 15 Broadcast The default gateway for APG43L and STOC is to be a VRRP-managed address, preferably in three address setup (one virtual router instance and no owner). In a two address VRRP configuration, the A-side and B-side switch addresses are to be used. If a switch failure occurs with a two address VRRP configuration, VRRP moves the failing switch IP address to the other switch transparently to the APG43L. STOC cannot take advantage of VRRP redundancy as it has a physical connection to only one BSC IP network interface. Note:

10

APG43L and STOC can stay directly connected to Site LAN even if the NWI-E are installed in the BSC. However, the subnet Internal_OM still has to be defined in the NWI-E.

9/198 17-APT 210 09 Uen AB | 2019-03-29

Configuration

Table 3

Host Address Allocation in Subnet OEN_BSC Host Function 0 Network number 1 A-side switch 2 A-side switch 3 OEN RP 4 not allocated 5 not allocated 6 not allocated 7 Broadcast

Table 4

Host Address Allocation in the IPS subnet (/23) for NWI-E and SMX Host Function 0.0 Network number 0.1 A-side switch 0.2 RP #1, A-side 0.3 RP #2, A-side ... 0.255 Reserved 1.0 Reserved 1.1 B-side switch 1.2 RP #1, B-side 1.3 RP #2, B-side ... 1.255 Broadcast

The IPS subnet is used by the IP Gateway Supervision (IPS) application. The IPS application monitors link status and move IP traffic from the A-side to the B-side, or the other way around, when a failure is detected. The gateway GW1 is set to the IP address of the A-side switch and GW2 to the B-side. For the NWI-E, and SMX the subnet IPS contains the IP addresses of both the A-side and the B-side. This can be seen in Table 4. In this configuration, it is also vital that the network mask in the NWI-E for IPS subnet matches the network mask in the RPs. The proposed address plan for NWI-E and SMX has a network mask of /23, or 255.255.254.0. See also Reference [2].

9/198 17-APT 210 09 Uen AB | 2019-03-29

11

BSC IP Addressing

Table 5

Host Address Allocation in Subnet GbIP

Host Function 0 Network number 1 A-side switch 2 B-side switch 3 GPH RP #1 4 GPH RP #2 ... No default gateway is to be configured for the IP addresses of the Gb over IP application, which is the application communicating on the GbIP subnet. Further information on Gb over IP configuration is found in Reference [2]. Table 6

Host Address Allocation in Subnet AbisIP

Host Function 0 Network number 1 A-side switch 2 B-side switch 3 "Floating" IP address 4 PGW RP #1 5 PGW RP #2 ... No default gateway is to be configured for the IP addresses of the Packet Abis over IP pplication, which is the application communicating on the AbisIP subnet. Further information on Abis over IP configuration is found in Reference [2]. Table 7

Host Address Allocation in Subnet SS7

Host Function 0 Network number 1 A-side switch 2 SIGTRAN RP #1 3 SIGTRAN RP #3 ... 9 B-side switch 10 SIGTRAN RP #2 11 SIGTRAN RP #4

12

9/198 17-APT 210 09 Uen AB | 2019-03-29

Configuration

Host Function ... 15 Broadcast The SIGTRAN application provides SS7 signaling over IP to the BSC and executes on the Signaling Link Interface (SLI) boards or directly on the CP if an Evo Controller 8200 and Evo Controller 8230 node is used. The subnet SS7 contains the IP addresses of all SLIs and their gateways. In the address plan proposed in Table 7, the SLIs are divided between an upper and lower part of the subnet. This is important as to maintain path separation for communication resilience. Hence, when supplying the subnet mask of the gateways during set-up of the SIGTRAN application, and the site routers, subnet masks corresponding to the upper and lower part of the SS7 subnet are to be used. Further information on SS7 over IP configuration is found in Reference [2]. Note:

SIGTRAN can be connected directly to the Site LAN even though the NWI-E are installed in the BSC except for Evo Controller 8200 and Evo Controller 8230 nodes. If so, then the subnet SS7 / Internal_SS7 does not have to be configured in the NWI-E.

Table 8

Host Address Allocation in Subnet A_userplane

Host Function 0 Network number 1 A-side switch 2 B-side switch 3 AGW RP #1 4 AGW RP #2 5 AGW RP #3 ... 15 Broadcast No default gateway is to be configured for the IP addresses of the AGW application, which is the application handling the communication with the MGW for A-Interface over IP. Further information on AGW configuration is found in Reference [2]. Table 9

Host Address Allocation in Subnet Intercon

Host Function 0 Network number 1 A-side switch 2 B-side switch 3 Broadcast

9/198 17-APT 210 09 Uen AB | 2019-03-29

13

BSC IP Addressing

The Intercon subnet is used for failover routing and each switch has one IP address, used as gateway, on the subnet. Intercon subnet is not used in SMX configuration. Table 10

Host Address Allocation in Subnet CBC

Host Function 0 Network number 1 A-side switch 2 B-side switch 3 SMS CBC IP ... 7 Broadcast No default gateway is to be configured for the IP addresses of the SMS Cell Broadcast application (CBS). Further information on CBS configuration is found in Reference [2].

2.2.3

External Subnets The BSC is accessed from the external subnets where the SGSN, OSS, and so on, reside. No requirements are put on these subnets from a BSC IP addressing perspective. IP address overlap is not supported at all.

2.2.4

VLAN Tags The VLAN tags used internally within the BSC are shown in Table 11. Table 11

VLAN name

Tag

Intercon

15

BSC_Inner

30

SS7_Inner or SS7_Inner_A

51 (mandatory - see below)

SS7_Inner_B

52 (mandatory - see below)

LH_A

45

LH_B

46

Note:

14

VLAN tags used internally by BSC NWI-E

SS7_Inner/ SS7_Inner_A/ SS7_Inner_B is only used by Evo Controller 8200. SS7_Inner_B is only mandatory in case when two separate SS7_Inner VLANs are used.

9/198 17-APT 210 09 Uen AB | 2019-03-29

Configuration

Table 12

VLAN tags used internally in SMX configuration

VLAN name

Tag

IPS

20

OM_Inner

900 (mandatory)

Gb_Inner

50

SS7_Inner or SS7_Inner_A

51 (mandatory)

SS7_Inner_B

52 (mandatory - see below)

Abis_Inner

60

A_userplane_Inner

62

CBC_Inner

65

EVOET_Ingress

180 (mandatory)

APZ-A, APZ-B

1 (mandatory)

APG-TIPC

33 (mandatory)

APG-DRBD

1206 (mandatory)

Note: — SS7_Inner_B is only mandatory in case when two separate SS7_Inner VLANs are used. — VLANs APZ-A, APZ-B, APG-TIPC, and APG-DRBD are created automatically at node start-up. VLAN tags 1, 33, 51, 52, 900 and 1206 are reserved by APZ and cannot be changed. SS7_Inner can be shared between A and B plane or two separate SS7_Inner VLANs can be used on A and B planes. In case of shared VLAN, tag 51 is used. In the case of two separate SS7_Inner VLANs, tag 51 is used on A plane and tag 52 on B plane. External VLAN tagging can be enabled for the interface toward the site routers, that is VLAN SR_OM, SR_Gb, SR_Abis, SR_A_userplane, SR_CBC and SR_SS7. This is further described in the OPIs in Reference [6]. There are two recommended setups of externally tagged VLANs: — One VLAN per traffic type, shared by all BSCs at the site — One VLAN per traffic type and BSC The VLAN tags can be chosen freely, but use tags numbered 100 or higher for external VLANs to clearly differentiate from internal VLAN tags that are to be

9/198 17-APT 210 09 Uen AB | 2019-03-29

15

BSC IP Addressing

allocated from the 1–99 range. Additional VLANs can be allocated within the range of 1–99 in future BSC releases.

2.2.5

VRID The recommended VRID allocation scheme depends on how VLAN tagging is used on the interface toward the site routers. If the interface toward the site routers is tagged and there is one VLAN allocated per traffic type and per BSC, allocate one or two VRIDs, as needed, and reuse these for all VLANs on all BSCs. Otherwise, allocate one or two VRIDs, as needed, per BSC and reuse these for all VLANs of that BSC. Each BSC will then have unique VRID or VRIDs. Note:

2.2.6

It is possible that different VRID allocation principles have been applied in previous versions of the configuration script, or the VRIDs have been changed manually by the user. Hence, this has to be taken care of if a new BSC node is introduced on a site LAN.

Quality of Service The BSC IP infrastructure provides overprovisioning for most BSC configurations, and normally does not require any additional setup to meet necessary quality of service (QoS) requirements for the different traffic types. The default configuration offers a best effort service to all traffic types in which all traffic types contend for the same bandwidth resource. If specific QoS requirements per traffic type have to be fulfilled, the BSC IP network interfaces can be set up to map physical port and/or Differentiated Services Code Point (DSCP) to one of eight queues. For more information on the QoS support, see Reference [14] for BSC NWI-E. SMX does not support DSCP mapping. For many of the BSC IP-based applications, a DSCP value can be set. However, certain BSC traffic types, notably OAM MML command and file transfer, cannot have its DSCP set and cannot be discriminated by the physical port used. For low-bandwidth site connections and/or QoS requirements, the minimum bandwidth that can be allocated by the BSC IP network interfaces to a traffic type can be too large. Also, site aggregation of traffic can render any extensive QoS implementation in the BSC IP network interfaces non-optimal. Hence, only set up the BSC IP network interfaces to minimize the latency for latency sensitive traffic types, such as Packet Abis over IP, and implement the QoS requirements at the site level. The BSC does not put any restrictions on the DSCP values used.

2.2.7

IP Configuration and Consistency Check Once the BSC IP network plan has been set, the various BSC IP enabled applications have to be configured accordingly. See Reference [2] for information

16

9/198 17-APT 210 09 Uen AB | 2019-03-29

Configuration

on how to set up the SS7 over IP, Gb over IP, Packet Abis over IP, GMLOG, RTT, OEN, A-Interface over IP, SMS CBC, and R-PMO applications. Information regarding the APG43L setup see Reference [1]. Documentation describing how to set up the BSC NWI-E is found in Reference [4]. Documentation describing how to set up the SMX is found in Reference [7]. After successful configuration of the BSC IP network interfaces a configuration consistency check shall be performed. This check is described in Reference [3].

2.3

Migration to BSC IP Connectivity For a description how to migrate a BSC to BSC IP Connectivity, see Reference [5].

9/198 17-APT 210 09 Uen AB | 2019-03-29

17

BSC IP Addressing

18

9/198 17-APT 210 09 Uen AB | 2019-03-29

Concepts

3

Concepts AGW RP

Regional Processor with AGW application.

APG43L

This includes the hardware variants APG43/2, APG43/3 and APG43/4.

BSC IP Network Interfaces The part of the BSC that provides IP connectivity to the different IP hosts within the BSC. Two implementations exist, BSC NWI-E, and SMX. BSC NWI-E

A hardware implementation of the BSC IP network interfaces. It consists of two single slot GEM/EGEM/EGEM2 boards, which can handle both Layer 2 and Layer 3.

CTH RP

Regional Processor with CTH application, combining AGW, PGW, and TRH functions.

Floating IP Address An IP address used by the PGW application but not bound to any specific RP board. Let all the STN and Baseband Radio 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 one plane of the BSC IP Network Interfaces is lost. If a connection fails, an alarm is raised, see Reference [11]. 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, RTT, 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-. For PGW the device owning block is RTIPPGW and the IP devices are named RTIPPGW-

PGW RP

Regional Processor with PGW application.

9/198 17-APT 210 09 Uen AB | 2019-03-29

19

BSC IP Addressing

20

SLI

Regional Processor with SIGTRAN application.

SMS CBC

SMS Cell Broadcast Center, an application providing an interface to external CBC servers for SMS cell broadcasts.

SMX

A hardware implementation of the BSC IP Network Interfaces. It consists of two double-slot EGEM2 boards. SMX handles L2/L3 switching in the BSC, including the EGEM2 backplane connectivity.

9/198 17-APT 210 09 Uen AB | 2019-03-29

Glossary

Glossary

AGW A-Interface Gateway

MSC Mobile Services Switching Center

APG Adjunct Processor Group

NAT Network Address Translation

BSC Base Station Controller

NTP Network Time Protocol

BTS Base Transceiver Station

NWI-E Network Interface - Ethernet

CBC Cell Broadcast Center

OAM Operation and Maintenance

CTH Combined Traffic Handler

OEN Open Event Notification Interface

DSCP Differentiated Services Code Point

OMT Operation and Maintenance Terminal

EGEM Enhanced Generic Ericsson Magazine

OSS Operations and Support System

EGEM2 Evolved Generic Ericsson Magazine, type 2

PCI Peripheral Component Interconnect

GMLOG GPRS/EGPRS Mobile Logging

PGW Packet Gateway

GPH GPRS Packet Handler

QoS Quality of Service

GPRS General Packet Radio Service

R-PMO Real-Time Performance Monitoring

IP Internet Protocol

RP Regional Processor

IPS IP Gateway Supervision

RPP Regional Processor with PCI Interface

LAN Local Area Network

RTT Real Time Trace

MGW Media Gateway

SGSN Serving GPRS Support Node

9/198 17-APT 210 09 Uen AB | 2019-03-29

21

BSC IP Addressing

SIGTRAN Signaling Transport SLI Signaling Link Interface SMLC Serving Mobile Location Center SMSCB Short Message Service Cell Broadcast SMX System Control and Main Switch SS7 Signaling System Number 7 SSH Secure Shell STN Site Transport Node STOC Signaling Terminal Open Communication VLAN Virtual Local Area Network VRID Virtual Router Identifier VRRP Virtual Router Redundancy Protocol

22

9/198 17-APT 210 09 Uen AB | 2019-03-29

Reference List

Reference List

Ericsson Documents [1]

AP, IP Address Change, Initiate OPERATIONAL INSTRUCTION

[2]

BSC IP Application Set Up USER GUIDE

[3]

BSC, IP Connectivity Consistency Check, Perform OPERATIONAL INSTRUCTION

[4]

BSC NWI-E Configuration USER GUIDE

[5]

BSC, NWI-E, Install OPERATIONAL INSTRUCTION

[6]

BSC, NWI-E, VLAN Tagging on Site Interface, Change OPERATIONAL INSTRUCTION

[7]

BSC SMX Configuration USER GUIDE

[8]

BSC/TRC and BSC Hardware Dimensioning Handbook DESCRIPTION

[9]

Evo Controller 8200/BSC and EvoC 8230 Hardware Dimensioning Handbook DESCRIPTION

[10] IP Infrastructure Subsystem (IIS) DESCRIPTION [11] RADIO TRANSMISSION IP GATEWAY FAULT OPERATIONAL INSTRUCTION Standards [12] Address Allocation for Private Internets, RFC 1597 [13] Classless Inter-Domain Routing (CIDR), RFC 1519 Other Documents [14] ExtremeXOS 16.2 User Guide USER GUIDE [15] ExtremeXOS Command Reference Guide for Release 16.2 USER GUIDE

9/198 17-APT 210 09 Uen AB | 2019-03-29

23