GSM/EDGE BSS, Operating

Documentation

Radio Access

BSC TRANSPORT SITE SOLUTION

RG20

Daughter Document

External L2/L3 Equipment

DN0976623

Issue 01C

Approval Date 2012-03-15

Confidential

DN0976623 © 2014 Nokia Networks 1 / 100

Issue 01C
 Disclaimer BSC TRANSPORT SITE SOLUTION

The information in this document applies solely to the hardware/software product (“Product”) specified herein, and only as
specified herein.
This document is intended for use by Nokia Networks' customers (“You”) only, and it may not be used except for the
purposes defined in the agreement between You and Nokia Networks (“Agreement”) under which this document is
distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form or means without the
prior written permission of Nokia Networks. If you have not entered into an Agreement applicable to the Product, or
if that Agreement has expired or has been terminated, You may not use this document in any manner and You are obliged to
return it to Nokia Networks and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You assume full responsibility
when using it. Nokia Networks welcome Your comments as part of the process of continuous development and
improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements concerning the suitability,
capacity, fitness for purpose or performance of the Product are given solely on an “as is” and “as available” basis in this document,
and Nokia Networks reserves the right to change any such information and statements without notice. Nokia
Networks has made all reasonable efforts to ensure that the content of this document is adequate and free of material
errors and omissions, and Nokia Networks will correct errors that You identify in this document. But, Nokia
Networks' total liability for any errors in the document is strictly limited to the correction of such error(s). Nokia
Networks does not warrant that the use of the software in the Product will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF AVAILABILITY,
ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN
RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA NETWORKS BE LIABLE FOR ANY
DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH
AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY
ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM
THIS DOCUMENT OR ITS CONTENT.
This document is Nokia Networks’ proprietary and confidential information, which may not be distributed or
disclosed to any third parties without the prior written consent of Nokia Networks.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of
their respective owners, and they are mentioned for identification purposes only.
Copyright © 2014 Nokia Networks. All rights reserved.

Important Notice on Product Safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully
read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of
this document or documentation set.

Nokia Networks is continually striving to reduce the adverse environmental effects of its products and services. We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle
product packaging and follow the recommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us
at Nokia Networks for any additional information.

DN0976623 © 2014 Nokia Networks 2 / 100

Issue 01C
Table of Contents

Table of Contents

1 Introduction ..................................................................................................... 9
1.1 Target and scope ............................................................................................ 9
1.2 Note for the reader ........................................................................................ 11

2 Concepts....................................................................................................... 12
2.1 Abbreviations ................................................................................................ 12
2.2 Concepts and terminology............................................................................. 15

3 External L2/L3 equipment in BSC RG20(BSS) on top ................................... 16

3.1 General ......................................................................................................... 16
3.2 BSC site with Ethernet based backhaul/backbone network ........................... 16
3.3 BSC site with TDM based backhaul network (TDM Ethernet media
conversion) ................................................................................................... 17

4 External L2/L3 equipment in bsc RG20(BSS) on top: CISCO products ......... 19

4.1 Overview on CISCO Routers and Switches Products.................................... 19
4.1.1 Portfolio overview .......................................................................................... 19
4.1.2 Model comparison ......................................................................................... 19
4.2 CISCO 7600 family ....................................................................................... 21
4.2.1 Architecture ................................................................................................... 21
4.2.2 Processor options ......................................................................................... 24
4.2.3 CISCO Line Cards suitable for RG20(BSS) on top Site solution.................... 28
4.2.4 BSC3i/Flexi BSC ........................................................................................... 28
4.2.5 mcBSC.......................................................................................................... 34
4.2.6 BSC Site with Media Conversion TDM – Ethernet ......................................... 35
4.2.7 Recommended System Configuration (7609) ................................................ 38
4.2.8 Alternative System Configuration (7604) ....................................................... 40
4.3 CISCO Management ..................................................................................... 40

5 BSC transport site solution: MLS Setup ........................................................ 41

5.1 Installation ..................................................................................................... 41
5.1.1 BSC3i/FlexiBSC and TCSM3i ....................................................................... 41
5.1.2 Stand-alone mcBSC and mcTC .................................................................... 47

DN0976623 © Nokia Networks 3 / 100

Issue 01C
Table of Contents

5.2 Provisioning overview.................................................................................... 51

5.2.1 L2&L3 ports setting ....................................................................................... 52
5.2.2 VLAN & SubNet setting ................................................................................. 52
5.2.3 MTU size ....................................................................................................... 52
5.2.4 Link aggregation............................................................................................ 52
5.2.5 HSRP and Default Gateway setting............................................................... 53
5.2.6 IGP setting .................................................................................................... 54
5.2.7 Multiple Spanning Tree Protocol (MSTP) ...................................................... 55
5.2.8 Ethernet OAM setting .................................................................................... 56
5.2.9 SyncE setting ................................................................................................ 58
5.2.10 Quality of Service (QoS)................................................................................ 58
5.2.10.1 L3 .................................................................................................................. 58
5.2.10.2 Packet marking in BSC/PTP-M/ATS.............................................................. 58
5.2.10.3 Packet classification/handling in Multilayer Switches ..................................... 59
5.2.10.4 L2 .................................................................................................................. 60
5.2.10.5 VLAN priority p-bits marking in BSC/PTP-M/ATS .......................................... 60
5.2.10.6 VLAN priority p-bits handling in MLSs ........................................................... 61
5.3 Provisioning examples BSC3i/FlexiBSC ........................................................ 61
5.3.1 Reference scenario #1 (Backbone/Backhaul L3) ........................................... 61
5.3.1.1 Overview ....................................................................................................... 61
5.3.1.2 L3 ports provisioning ..................................................................................... 64
5.3.1.3 VLAN & Subnet provisioning ......................................................................... 64
5.3.1.4 L2 port provisioning ....................................................................................... 65
5.3.1.5 HSRP provisioning ........................................................................................ 66
5.3.2 Reference scenario #2 (Backbone L3 + Backhaul L2) ................................... 67
5.3.2.1 Overview ....................................................................................................... 67
5.3.2.2 L3 ports provisioning ..................................................................................... 70
5.3.2.3 VLAN& Subnet provisioning .......................................................................... 70
5.3.2.4 L2 port provisioning ....................................................................................... 72
5.3.2.5 HSRP provisioning ........................................................................................ 73
5.3.3 Reference scenario with IPSEC .................................................................... 74
5.3.3.1 Overview ....................................................................................................... 74

DN0976623 © 2014 Nokia Networks 4 / 100

Issue 01C
5.3.3.2 L3 ports provisioning ..................................................................................... 77
5.3.3.3 VLAN & Subnet provisioning ......................................................................... 77
5.3.3.4 L2 port provisioning ....................................................................................... 78
5.3.3.5 PBR (Policy based routing) ........................................................................... 80
5.3.3.6 HSRP provisioning ........................................................................................ 85
5.3.3.7 OSPF ............................................................................................................ 86
5.4 Provisioning examples: mcBSC .................................................................... 86
5.4.1 Reference scenario #1 (Backbone/Backhaul L3) with no mcTC .................... 86
5.4.1.1 Overview ....................................................................................................... 86
5.4.1.2 L3 port provisioning ....................................................................................... 87
5.4.1.3 VLAN & Subnet provisioning ......................................................................... 87
5.4.1.4 L2 port provisioning ....................................................................................... 89
5.4.1.5 HSRP provisioning ........................................................................................ 90
5.4.2 Reference scenario #1 (Backbone/Backhaul L3) with remote mcTC ............. 91
5.4.2.1 Overview ....................................................................................................... 91
5.4.2.2 L3 port provisioning ....................................................................................... 92
5.4.2.3 VLAN & Subnet provisioning ......................................................................... 92
5.4.2.4 L2 port provisioning ....................................................................................... 94
5.4.2.5 HSRP provisioning ........................................................................................ 94
5.4.3 Others ........................................................................................................... 95
5.4.3.1 Reference scenario #2 (Backbone L3 + Backhaul L2) ................................... 95
5.4.3.2 Scenarios with IPSEC ................................................................................... 96

6 Appendices ................................................................................................... 97
6.1 Juniper Products ........................................................................................... 97
6.1.1 Overview on JUNIPER Products (Routers and Switches) ............................. 97
6.1.2 Portfolio overview .......................................................................................... 97
6.1.3 Product comparison ...................................................................................... 98

DN0976623 © Nokia Networks 5 / 100

Issue 01C
List of Figures

List of Figures

Figure 1: BSC Transport Site Solution documentation structure................................................ 10

Figure 2: BSC Site Solution overview - Ethernet based backhaul/backbone ............................. 17
Figure 3: BSC Site Solution overview - Ethernet based backbone and TDM based backhaul ... 18
Figure 4: CISCO 7609-S ........................................................................................................... 22
Figure 5: CISCO 7600 Series Router Switch Processor 720 (RSP720) .................................... 25
Figure 6: CISCO 7600 Series Supervisor Engine 720 (Sup720) ............................................... 25
Figure 7: CISCO Catalyst 6500 48-port 10/100/1000 GbE Module ........................................... 28
Figure 8: CISCO Catalyst 6500 Series Mixed Media Gigabit (24 and 48 ports) ......................... 29
Figure 9: CISCO 7600 Series Ethernet Service Plus (ES+)....................................................... 30
Figure 10: CISCO 7600 Series Ethernet Service Plus XT (ES+ XT) .......................................... 31
Figure 11: CISCO 7600 Series Ethernet Service Plus XC (ES+ XC) ......................................... 32
Figure 12: CISCO 7600 Series Ethernet Service Plus T (ES+ T) .............................................. 33
Figure 13: CISCO Catalyst 6500 8-port 10 GbE module ........................................................... 34
Figure 14: CISCO 1-Port Channelized STM-1/OC-3 SPA ......................................................... 35
Figure 15: CISCO SIP-200 and SIP-400 ................................................................................... 36
Figure 16: MLS deployment reference model............................................................................ 45
Figure 17: MLS reference model (with Link Aggregation at Backbone/Backhaul/SGW/ATS) .... 46
Figure 18: MLS deployment reference model – Stand-alone mcBSC ........................................ 49
Figure 19: MSTP in BSC Transport Site Solution (L2 Backhaul, L3 connectivity between
SWU and MLS) .................................................................................................................. 56
Figure 20: Ethernet OAM Concept for RG20(BSS) on top......................................................... 57
Figure 21: Example of MLS configuration (Backbone L3 and Backhaul L3) .............................. 64
Figure 22: Example of MLS configuration (Backbone L3 and Backhaul L2) .............................. 70
Figure 23: IPSEC Network scenario: Traffic split through SGWs............................................... 74
Figure 24: Example of MLS configuration (Backbone L3 and Backhaul L3 + IPSEC) ................ 77
Figure 25: IPSEC Network scenario: Traffic split through SGWs (mcBSC) ............................... 96

DN0976623 © 2014 Nokia Networks 6 / 100

Issue 01C
List of Tables

List of Tables
Table 1: Abbreviations .............................................................................................................. 12
Table 2: Concepts and Terminology ......................................................................................... 15
Table 3: CISCO products - comparison and Nokia advice ......................................................... 20
Table 4: CISCO 7600 series routers – platform overview .......................................................... 23
Table 5: CISCO 7600 Series Router Switch Processor 720 (RSP720) ..................................... 26
Table 6: CISCO 7600 Series Supervisor Engine 720 (SUP720) product description ................. 26
Table 7: CISCO 7600 series routers – STM-1/OC-3 interface modules comparison ................. 37
Table 8: CISCO 7600 Recommended Chassis and cards ......................................................... 38
Table 9: MLS Port type/usage – FlexiBSC ................................................................................ 47
Table 10: MLS Port type/usage – Stand-alone mcBSC ............................................................. 50
Table 11: DSCP marking .......................................................................................................... 59
Table 12: Site equipment queue mapping (example, 4 queues)................................................ 60
Table 13: Site equipment queue mapping (example, 4 queues)................................................ 60
Table 14: Packet Abis (mapping between DSCP PHB and VLAN priority) ................................ 61
Table 15: L3 port provisioning (reference scenario #1) ............................................................. 64
Table 16: VLANs/Subnet provisioning (reference scenario #1) ................................................. 65
Table 17: SVI (reference scenario #1) ...................................................................................... 65
Table 18: L2 port provisioning (Flexi BSC; reference scenario #1) ............................................ 65
Table 19: HSRP configuration (FlexiBSC;reference scenario #1)............................................. 66
Table 20: L3 port provisioning (FlexiBSC; network scenario #2) ............................................... 70
Table 21: VLANs/Subnet provisioning (FlexiBSC; network scenario #2) .................................. 71
Table 22: SVI (network scenario #2) ......................................................................................... 71
Table 23: L2 port provisioning (FlexiBSC; network scenario #2) ............................................... 72
Table 24: HSRP configuration (FlexiBSC; network scenario #2) ............................................... 73
Table 25: L3 port provisioning (network scenario #1 with IPSEC) ............................................. 77
Table 26: VLANs/Subnet provisioning (FlexiBSC; network scenario #1 with IPSEC) ............... 78
Table 27: SVI (network scenario #1 with IPSEC) ...................................................................... 78
Table 28: L2 port provisioning (FlexiBSC; network scenario #1 with IPSEC) ............................ 78
Table 29: PBR configuration in MLS-0 (FlexiBSC; network scenario #1 with IPSEC) ................ 81
Table 30: PBR configuration in MLS-1 (FlexiBSC; network scenario #1 with IPSEC) ................ 83
Table 31: HSRP configuration (FlexiBSC; reference scenario #1 with IPSEC) .......................... 85
Table 32: L3 port provisioning (mcBSC; reference scenario #1; no mcTC) ............................... 87
Table 33: VLAN/Subnet provisioning (mcBSC; reference scenario #1; no mcTC) ..................... 87
Table 34: SVI (mcBSC; reference scenario #1; no mcTC) ........................................................ 88
Table 35: L2 port provisioning (mcBSC; reference scenario #1; no mcTC) ............................... 89
Table 36: HSRP configuration (mcBSC; reference scenario #1; no mcTC) ............................... 90
Table 37: L3 port provisioning (mcBSC; reference scenario #1; remote mcTC) ........................ 92
Table 38: VLAN/Subnet provisioning (mcBSC; reference scenario #1; remote mcTC) .............. 92
Table 39: SVI (mcBSC; reference scenario #1; remote mcTC) ................................................. 93
Table 40: L2 port provisioning (mcBSC; reference scenario #1; remote mcTC) ........................ 94
Table 41: HSRP configuration (mcBSC; reference scenario #1; remote mcTC) ........................ 95
Table 42: Juniper products - comparison and Nokia advice ...................................................... 98

DN0976623 © Nokia Networks 7 / 100

Issue 01C
Summary of Changes

Summary of Changes

Changes between document issues are cumulative. Therefore, the latest document issue
contains all changes made to previous issues.

Changes made between issues 01C and 01B

Removed combined mcBSC information.

Changes made between issues 01B and 01A

Updated the document with RG20(BSS) on top information.

Changes made between issues 01A and 01

Updated the document with some editorial changes.

DN0976623 © 2014 Nokia Networks 8 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION Introduction

1 Introduction

1.1 Target and scope

The present document is part of a set of documents describing the BSC Site
Solution for RG20(BSS) on top (see Figure 1 for the related documentation
structure).
The aim of the document is to describe the recommended external L2/L3
equipment type(s) to be used for the BSC connection to the transport
(backhaul/backbone) networks.
This document describes the external equipment in terms of high level
functional description, setup and configuration (not the used commands) in
relation to the reference use cases as listed in the BSC Transport Site
Solution Mother Document /A/.
HW and SW architecture of the external equipment is out of the scope of this
document.

DN0976623 © 2014 Nokia Networks 9 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION Introduction

Figure 1: BSC Transport Site Solution documentation structure

DN0976623 © 2014 Nokia Networks 10 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION Introduction

1.2 Note for the reader

In this document ETP is used for both ETP and ETIP.

DN0976623 © 2014 Nokia Networks 11 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION Concepts

2 Concepts

2.1 Abbreviations

Table 1: Abbreviations

ABBR Explanation
AF Assured Forwarding

aka also known as

APS Automatic Protection Switching

ATS Adaptive Timing Server

BB BackBone

BBI BSC-BSC Interface

BCSU Base Station Controller Signalling Unit

BE Best Effort

BH BackHaul

BSC Base Station Controller

BTS Base Transceiver Station

CBS Cell Broadcast Service

DN0976623 © 2014 Nokia Networks 12 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION Concepts

ABBR Explanation
CoS Class of Service

DSCP DiffServ Code Point

DWRR Deficit Weighted Round Robin

EF Expedited Forwarding

En European hierarchical Digital Interface, PDH

ETH Ethernet

ETIP Exchange Terminal for IP PWE

ETP Exchange Terminal for Packet

ETPA Exchange Terminal for Packet A-interface

ETPC Exchange Terminal for Packet A-interface in Transcoder

ETPE Exchange Terminal for Packet over Ethernet

FE Fast Ethernet

GbE Gigabit Ethernet

GE Gigabit Ethernet

GERAN GSM EDGE Radio Access Network

IP Internet Protocol

L1 Layer 1

L2 Layer 2

L3 Layer 3

ME Metro Ethernet

Mpps Mega packet per second

OAM Operation, Administration and Maintenance

O&M Operation and Maintenance

OC-3 Optical Carrier level-3

DN0976623 © 2014 Nokia Networks 13 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION Concepts

ABBR Explanation
PCU Packet Control Unit

PDH Plesiochronous Digital Hierarchy

PHB Per Hop Behaviour

PSN Packet Switched Network

PTP-M PTP-Master

PW Pseudo Wire

PWE Pseudo Wire Emulation

QoS Quality of Service

RFC Requests For Comments

RJ-45 Registered Jack type 45

RU Rack Unit

SGW Security GateWay

SFP Small Form Factor Pluggable

SGW Security GateWay

SIP SPA Interface Processor

SPA Shared Port Adapter

SSE Site Support Equipment

TC TransCoder

TCSM TransCoder SubMultiplexer

TDM Time-division Multiplexing

ToP Time over Packet

VC Virtual Container

VLAN Virtual LAN

DN0976623 © 2014 Nokia Networks 14 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION Concepts

ABBR Explanation
VNP Vendor Network Probr server

WRR Weighted Round Robin

WRED Weighted Random Early Detection

XFP 10 Gbit Small Form Factor Pluggable

2.2 Concepts and terminology

Table 2: Concepts and Terminology

Backbone Network Packet Switched Network between BSC Site and CN/NetAct.
Backhaul Network Packet Switched Network between BSC site and the controlled BTSs.
External ETPSIG BSC-TCSM ETP Signalling (C/M-plane) interface
Signalling (C/M-plane) between BSC (BCSU) and TCSM (ETPC) in AoIP
with TC in BSS scenario.
Configuration Definition: Description of how the hardware and software of a system are
arranged at a given point of time.
Installation Definition: The process of placing equipment or software in position, and
connecting and adjusting it for use.

Installation includes the installation of software and configurations

done in connection with the installation and commissioning. For example,
tasks that are performed to enable a network element to be mounted at the
site, including mounting and fixing the rack and plug-in units, and running the
internal and external cabling.
Commissioning Definition: The process of bringing software or hardware into use for the first
time.
Provisioning Definition: The process of making the resource available for the user.

Provisioning an account or service may involve the creation,

modification, deletion, suspension, and restoration of a defined set of
accounts or attributes.

DN0976623 © 2014 Nokia Networks 15 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in BSC RG20(BSS) on top

3 External L2/L3 equipment in BSC

RG20(BSS) on top

3.1 General
The BSC Site Solution for RG20(BSS) on top assumes the deployment of a
pair of L2/L3 site equipment for BSC connection to the transport
(backhaul/backbone) network.
Nokia recommends the use of MultiLayer Site Switches which can be based on
CISCO products.
Such MultiLayer Switch (MLS) pair should be able to connect all BSC external
interfaces as well as all interfaces to/from optional equipment at the BSC site
(for example, External Sync Master, SGW, SSE Manager).

3.2 BSC site with Ethernet based backhaul/backbone

network
Figure 2 depicts the BSC site solution for RG20(BSS) on top when both
backbone and backhaul are Ethernet based. Scenarios and requirements for
external devices are described in BSC Transport Site Solution Mother
Document /A/.

DN0976623 © 2014 Nokia Networks 16 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in BSC RG20(BSS) on top

BSC Site
BSC
TCSM

DCN/BackBone Network SGW

L3
MLS SGW

Backhaul Network MLS ATS

L2 or L3

SSE-M PTP-M

Figure 2: BSC Site Solution overview - Ethernet based backhaul/backbone

3.3 BSC site with TDM based backhaul network (TDM

Ethernet media conversion)

Figure 3. depicts the BSC site solution for RG20(BSS) on top when backbone
is Ethernet based whereas backhaul is instead TDM based with Transport
Media Conversion (TDM Ethernet) functionality being integrated in the
MLSs. The latter are therefore interfacing the BSC via Ethernet and the
backhaul via TDM (i.e. STM-1/OC-3). Such a scenario and related
requirements for external devices are described in BSC Transport Site
Solution Mother Document /A/.

DN0976623 © 2014 Nokia Networks 17 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in BSC RG20(BSS) on top

Figure 3: BSC Site Solution overview - Ethernet based backbone and TDM based backhaul

Use of PDH E1/T1 ports would be a further possibility for the TDM based
backhaul.
Moreover, even though not in the scope of Transport Media Conversion
feature, in principle it would be possible to have TDM based backbone (e.g.
for A or Gb interface towards the Core). In this case ML-PPP can be used
back to back between CISCO devices (i.e. between Cisco MLSs located in
BSC site and CISCO equipments located in the Core Network site(s)), this
being transparent from BSC perspective. For this kind of scenario the use of
high order virtual containers, such as VC3 or VC4, can be considered as more
efficient than using the low order VC12.

DN0976623 © 2014 Nokia Networks 18 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

4 External L2/L3 equipment in bsc

RG20(BSS) on top: CISCO products

4.1 Overview on CISCO Routers and Switches

Products

4.1.1 Portfolio overview

CISCO offers a wide variety of products (from Routers to Switches) that can in
principle fulfill the needs of the BSC site external L2/L3 equipment.
In general CISCO 7600 router models are considered suitable for all
configurations as well as all use cases in RG20. CISCO 7609 is the chosen
solution for 3G (RNC site external equipment) and therefore the ideal
candidate for BSC-RNC co-sitting.
CISCO Catalyst 3750 switch is also suitable. However, it has some limitations
like in some use cases; it does not provide the full set of required features (for
example, SyncE, Ethernet OAM).
In the customer environment there might be other CISCO models already
installed which are in principle suitable as well but they are not tested by Nokia
or they are not suitable for RG20(BSS) on top needs.

4.1.2 Model comparison

A comparison of the most relevant CISCO Models is summarized in the

following table, which includes technical limitations and an indication of what is
the recommended choice from Nokia perspective.

DN0976623 © 2014 Nokia Networks 19 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

Table 3: CISCO products - comparison and Nokia advice

Technical
Mode Nokia Advice Remarks
Limitations
7600 Suitable in all use cases and tested by
Nokia.
Router
Due to the large number of ports, it can
ETH-LM is not be used in big configurations.
Recommended The 7609 model is recommended in
supported.
WCDMA, likely to be used in case of co-
siting with RNC.

Ethernet WAN
1
3750 Interfaces only. Not suitable in all use cases. Used/tested
SyncE not in the Nokia Labs.
Catalyst Switch supported. It provides only Ethernet interfaces and it
Suitable with
Ethernet OAM cannot be used if SyncE is required (or
limitation
supported only Ethernet OAM unless using the ME
on Metro version).
Ethernet
version.

DN0976623 © 2014 Nokia Networks 20 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

Technical
Model Nokia Advice Remarks
Limitations
Not suitable in all use cases and not
4500 Catalyst tested by Nokia.
Switch It provides only Ethernet interfaces and
Suitable with cannot be used if SyncE is required.
SyncE not Not Recommended because not tested
limitation / Not
supported. by Nokia.
Recommended
Listed here because some Operators
might already have this equipment in the
field.
Not suitable in all use cases and not
tested by Nokia.
6500 Catalyst Similar to 7600 as far as routing is
Switch concerned, but mainly used for campus
Suitable with application.
SyncE not
limitation / Not
supported. Not recommended because not tested by
Recommended
Nokia.
Listed here because some Operators
might already have this equipment in the
field.
Not suitable in all use cases. Cannot
7200 SyncE not cope with the high number of GE ports
Router supported. required by PWE, Packet Abis and AoIP
Suitable with (might in principle be used in case of
Ethernet OAM
limitation / Not GboIP only).
not supported.
recommended
Very low GE Listed here because some Operators
ports density. might already have this equipment in the
field.

1
CISCO 3750 and 3760 are very close to each other. Only difference between CISCO 3750 and
3760 is stacking interface. If there is no need to expand configurations by adding new boxes,
then 3760 suitable.

4.2 CISCO 7600 family

4.2.1 Architecture

CISCO 7600 is one of the industry-leading carrier-class edge router

offering integrated, high-density Ethernet switching, IP/MPLS routing
and a variety of interfaces among which Ethernet (1/10 Gbps) and TDM

DN0976623 © 2014 Nokia Networks 21 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

(E1/T1, STM-1/OC-3). As of today CISCO 7600 series comprises 5 main

models which are different in size and performance/capacity. Each
model has its own chassis and it is offered with a different number of
configurable interface slots:
• One slot hosting the supervisor processor card
• Second slot hosting a second (optional) redundant supervisor
processor card
• Additional slots (number depends on model) used for all line cards
depending on the needs.
CISCO 7609-S is shown in Error! Reference source not found.Figure 4. and
a high level model comparison is shown in the Table 4.

Supervisor
Cards Line
Cards

Figure 4: CISCO 7609-S

DN0976623 © 2014 Nokia Networks 22 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

Table 4: CISCO 7600 series routers – platform overview

Feature 7603-S 7604 7606(-S) 7609(-S) 7613

7603(-S) 7604 7606(-S) 7609(-S) 7613

Processor Supervisors: Supervisors: Supervisors: Supervisors: Supervisors:

RSP720-3C, RSP720-3C, RSP720-3C, RSP720-3C, RSP720-3C,
RSP720-3CXL RSP720-3CXL RSP720- RSP720-3CXL RSP720-
3CXL 3CXL
Sup720-3B, Sup720-3B, Sup720-3B,
Sup720-3B, Sup720-3B,
Sup720-3BXL, Sup720-3BXL, Sup720-3BXL,
Sup720- Sup720-
Sup32 Sup32 Sup32
3BXL, 3BXL,
Sup32 Sup32
Slots 3 (horizontal) 4 (horizontal) 6 (horizontal) 9 (vertical) 13
(horizontal)
Forwarding up to 96 Mpps up to 144 Mpps up to 240 up to 400 Mpps up to 400
Mpps Mpps
Rate
Distributed
Backplane 240 Gbps 320 Gbps 480 Gbps 720 Gbps 720 Gbps
Capacity
Fixed Ports SFP and SFP and SFP and SFP and SFP and
10/100/1000 10/100/1000 10/100/1000 10/100/1000 10/100/1000
(RSP720, (RSP720, (RSP720, (RSP720, (RSP720,
Sup720) Sup720) Sup720) Sup720) Sup720)
WAN DS0 to OC-192 DS0 to OC-192 DS0 to OC- DS0 to OC-192 DS0 to OC-
192 192
Interface
Range
LAN 10 Mbps to 10 Mbps to 10 Mbps to 10 Mbps to 10 Mbps to
Interface 10 Gbps 10 Gbps 10 Gbps 10 Gbps 10 Gbps
Range

DN0976623 © 2014 Nokia Networks 23 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

Feature 7603-S 7604 7606(-S) 7609(-S) 7613

Internal DC AC or DC AC or DC AC or DC AC or DC
Power Supply
Chassis 4 RU 5 RU 7 RU 21 RU 19 RU
Height
(7-foot) Rack up to 11 per up to 9 per rack up to 6 per up to 2 per rack up to 2 per
rack rack rack
Mountable
Density
Dimensions 7 x 17.37 x 8.75 x 17.5 x 12.2 x 17.25 36.75 x 17.2 x 33.3 x 17.2 x
x
(H x W x D) 20.3 in. 21.75 in. 20.7 in. 18.1 in.
21.5 in.
(17.78 x 44.12 x (22.225 x 44.45 (93.3 x 43.1 x (82.3 x 42.5
x 55.245 cm) (30.98 x x
51.56 cm) 53.3 cm)
43.81 x
44.7 cm)
54.61 cm)

4.2.2 Processor options

As processor card there are different options (RSP720-3C, RSP720-3CXL,

Sup720-3B, Sup720-3BXL, Sup32).
Nokia recommends CISCO 7600 Series Router Switch Processor 720
(RSP720).

Note:
This section includes the characteristics of RSP720 and
Sup720 as in CISCO Data sheet. For details please refer
to CISCO documentation.

DN0976623 © 2014 Nokia Networks 24 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

http://www.cisco.com/en/US/prod/collateral/routers/ps368/product_data_sheet0900aecd8057
f3b6.html

Figure 5: CISCO 7600 Series Router Switch Processor 720 (RSP720)

http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/product_data_sheet0918
6a0080159856.html

Figure 6: CISCO 7600 Series Supervisor Engine 720 (Sup720)

DN0976623 © 2014 Nokia Networks 25 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

Table 5: CISCO 7600 Series Router Switch Processor 720 (RSP720)

Description Specification

Software compatibility CISCO 7600 Series

®
RSP 720 is introduced on CISCO IOS Software Release 12.2.33SRB
train

Protocols Layer 3 routing protocols, Border Gateway Protocol version 4

(BGPv4), Open Shortest Path First (OSPF), Intermediate System-to-
Intermediate System (IS-IS), Routing Information Protocol (RIP),
Distributed Forwarding Information Base (FIB) switching, CISCO
Discovery Protocol, and Internet Control Message Protocol (ICMP)
Multicast forwarding, Protocol independent Multicast (PIM) (both
sparse and dense mode), (S,G), (*,G), and Bidirectional PIM in
hardware
Comprehensive MPLS support
CISCO Group Management Protocol and Internet Group Management
Protocol (IGMP) snooping

Reliability and availability Fast software upgrade (FSU)

Router Processor Redundancy+ (RPR+)
Stateful Switchover + Nonstop Forwarding (SSO + NSF)
Online insertion and removal (OIR) hot-swap

MIBs MPLS LDP MIB, MPLS Label Switch Router (LSR) MIB, MPLS-TE
MIB, and MPLS VPN MIB; refer to software release notes for
additional information
Check the following MIB finder for more information:
http://www.Cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.

Network management CISCOWorks

Table 6: CISCO 7600 Series Supervisor Engine 720 (SUP720) product description

Product Specifications

Software CISCO 7600 Series

Compatibility
WS-SUP720 supports CISCO IOS 12.2(14)SX2 and later

DN0976623 © 2014 Nokia Networks 26 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

Product Specifications

WS-SUP720-3B supports CISCO IOS 12.2(17d)SXB1 and later

WS-SUP720-3BXL supports CISCO IOS 12.2(17b)SXB and later

Protocols Layer 3 routing protocols, Border Gateway Protocol version 4 (BGPv4), Open
Shortest Path First (OSPF), Intermediate System-to-Intermediate System (IS-IS),
Enhanced Interior Gateway Routing Protocol(EIGRP), Routing Information Protocol
(RIP), Distributed FIB Switching, CISCO Discover Protocol (CDP), Internet Control
Message Protocol (ICMP)
Traditional Protocols such as Internetwork Packet Exchange (IPX), Appletalk,
DECnet, Virtual Integrated Network Service (VINES), Connectionless Network
Service (CLNS)
Multicast forwarding, Protocol independent Multicast (PIM) (both sparse and dense
mode), (S,G), (*,G), Bi-Directional PIM in hardware
Comprehensive MPLS support
CISCO Group Management Protocol and Internet Group Management Protocol
(IGMP) snooping

Memory WS-SUP720 supports 512MB of DRAM for the router processor and 512 MB for the
switch processor
WS-SUP720-3B supports 512MB of DRAM for the router processor and 512 MB for
the switch processor, upgradeable to 1GB
WS-SUP720-3BXL supports 1GB DRAM for router the processor and 1GB DRAM for
the switch processor
64MB or 512MB (s/w image dependent) Boot Flash for SP switch processor and 64-
MB of Boot Flash for the router processor

Options Removable storage: 64MB, 128 MB, 256 MB, 512 MB (Compact Flash)

Uplink Ports Two Gigabit Ethernet ports, one Small Form-Factor Pluggable (SFP), one selectable
SFP or 10/100/100 RJ-45

Console Ports One (RS-232)

Reliability and FSU (Fast software upgrade)

Availability
RPR+ (Router Processor Redundancy+)
SSO+NSF (Stateful Switchover + Nonstop Forwarding)
OIR (Online insertion and removal) Hot Swap

MIBs MPLS LDP MIB, MPLS Label Switch Router (LSR) MIB, MPLS-TE MIB, MPLS VPN
MIB
Check the following MIB finder for more info: http://www.Cisco.com/public/sw-
center/netmgmt/cmtk/mibs.shtml

DN0976623 © 2014 Nokia Networks 27 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

Product Specifications

Network CISCO Works

Management

4.2.3 CISCO Line Cards suitable for RG20(BSS) on top Site solution

Note:
For details please refer to CISCO documentation at the
following link:
http://www.Cisco.com/en/US/products/hw/routers/ps368/p
roducts_relevant_interfaces_and_modules.html

CISCO 7600 provides a multitude of options to scale WAN connectivity from

DS-0 to OC-192 and LAN connectivity from 10 Mbps Ethernet through 10
Gbps Ethernet.

4.2.4 BSC3i/Flexi BSC

LAN interface modules. Recommended options are:

• CISCO Catalyst 6500 48-port 10/100/1000 GbE Module, RJ-
45 [WS-X6748-GE-TX]

Figure 7: CISCO Catalyst 6500 48-port 10/100/1000 GbE Module

WAN interface modules may be required to connect the site routers to the Ethernet based
Transport Network(s). Recommended options are:

DN0976623 © 2014 Nokia Networks 28 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

• CISCO Catalyst 6500 Series Mixed Media Gigabit

- Catalyst 6500 24-port GbE Module for SFPs [WS-X6724-
SFP]
- Catalyst 6500 48-port GbE Module for SFPs [WS-X6748-
SFP]

http://www.Cisco.com/en/US/prod/collateral/switches/ps5718/ps708/product_data_sheet090
0aecd801459a7.html

Figure 8: CISCO Catalyst 6500 Series Mixed Media Gigabit (24 and 48 ports)

• CISCO 7600 Series Ethernet Service Plus (ES+)

- CISCO 7600 Series Ethernet Services Plus 20G Line
Card, 2-port 10 GE XFP and DFC-3C [7600-ES+2TG3C]
- CISCO 7600 Series Ethernet Services Plus 40G Line
Card, 4-port 10 GE XFP and DFC-3C [7600-ES+4TG3C]
- CISCO 7600 Series Ethernet Services Plus 20G Line
Card, 20-port GE SFP and DFC-3C [7600-ES+20G3C]
- CISCO 7600 Series Ethernet Services Plus 40G Line
Card, 40-port GE SFP and DFC-3C [7600-ES+40G3C]

DN0976623 © 2014 Nokia Networks 29 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

http://www.cisco.com/en/US/prod/collateral/routers/ps368/data_sheet_c78-49152.html

Figure 9: CISCO 7600 Series Ethernet Service Plus (ES+)

CISCO 7600 Series Ethernet Service Plus XT (ES+ XT)

DN0976623 © 2014 Nokia Networks 30 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

CISCO 7600 Series ES Plus XT, LAN/WAN PHY, OTN/G.709, 2x10GE, XFP, DFC3C [76-
ES+XT-2TG3C]
CISCO 7600 Series ES Plus XT, LAN/WAN PHY, OTN/G.709, 4x10GE, XFP, DFC3C [76-
ES+XT-4TG3C]

http://www.cisco.com/en/US/prod/collateral/routers/ps368/data_sheet_c78-549419.html

Figure 10: CISCO 7600 Series Ethernet Service Plus XT (ES+ XT)

• CISCO 7600 Series Ethernet Service Plus XC (ES+ XC)

- CISCO 7600 ES+XC Combo 10x1GE/ 1x10GE, DFC3C [76-
ES+XC-20G3C]
- CISCO 7600 ES+XC Combo 20x1GE/ 1x20GE, DFC3C [76-
ES+XC-40G3C]

DN0976623 © 2014 Nokia Networks 31 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

http://www.cisco.com/en/US/prod/collateral/routers/ps368/data_sheet_c78-570732.html

Figure 11: CISCO 7600 Series Ethernet Service Plus XC (ES+ XC)

• CISCO 7600 Series Ethernet Service Plus T (ES+ T)

- CISCO 7600 Series ES Plus Transport, 20xGE ports,

SFP [76-ES+T-20G]
- CISCO 7600 Series ES Plus Transport, 40xGE ports,
SFP [76-ES+T-40G]
- CISCO 7600 Series ES Plus Transport, LAN/WAN PHY,
OTN/G.709, 2x10GE, XFP [76-ES+T-2TG]
- CISCO 7600 Series ES Plus Transport, LAN/WAN PHY,
OTN/G.709, 4x10GE, XFP [76-ES+T-4TG]

DN0976623 © 2014 Nokia Networks 32 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

http://www.cisco.com/en/US/prod/collateral/routers/ps368/data_sheet_c78-570732.html

Figure 12: CISCO 7600 Series Ethernet Service Plus T (ES+ T)

Recommended SFPs/XFPs for Ethernet line cards are:

• For Catalyst 6500 SFP [WS-X6724/6748-SFP] line cards
o 1000BASE-LX/LH SFP [GLC-LH-SM] for optical
transmission
o 1000BASE-T SFP [GLC-T] for electrical transmission
• For Ethernet Services [76-ES+] line cards
o Multirate XFP module for 10GBASE-LR and OC192 SR-1
[XFP-10GLR-OC192SR]
o 1000BASE-LX/LH SFP (DOM) [SFP-GE-L] 2
• For 10 GbE LAN [WS-X6708] line card
o 10GBASE-LR X2 module [X2-10GB-LR]

2
Additional SFP variants are available: covering Short Haul Optical (1000BASE-SX),
Extended Haul Optical (1000BASE-ZX) as well as Electrical (1000BASE-T).

DN0976623 © 2014 Nokia Networks 33 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

In case a 10 GbE interconnection between the two routers is considered, the following
unit could be used for cost-efficient implementation:
Catalyst 6500 8-port 10 GbE module [WS-X6708-10G-3C]
WS-X6708-10G-3C is less applicable as Backhaul WAN interface unit due to limitations in
queuing and shaping while backbone ports usually do not use shaping because it is not
reasonable to limit bandwidth.

http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/product_data_sheet0918
6a00801dce34_ps4835_Products_Data_Sheet.html

Figure 13: CISCO Catalyst 6500 8-port 10 GbE module

In case SyncE is the chosen synchronization solution for network synchronization, the line
card(s) has to be mandatorily selected among the ES+ unit options and variants.
The selection of which ES+ version to use depends on the needs of the operator. All versions
are supported by IOS 12.2 (33) SRD Software with the sole exception of ES+XC Combo
which requires SRE release (or later). ES+XC Combo version provides great flexibility in
terms of Ethernet interfaces (10/20x1GE and 1/2x10GE) on the very same card.

4.2.5 mcBSC

Interface modules for the connection of the site routers to mcBSC are essentially the same
as the ones defined in sub. 5.2.3.1 in the BSC3i/FlexiBSC case.
The only additional option, that can be considered as mcBSC only, is the possibility to
interface mcBSC via 10GE ports rather than GE ports. This is however not the Nokia
recommended option in RG20(BSS) on top.
The CISCO interface module for such an option would be the Catalyst 6500 8-port 10 GbE
module [WS-X6708-10G-3C] already mentioned in sub. 5.2.3.1 for site routers
interconnection.

DN0976623 © 2014 Nokia Networks 34 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

4.2.6 BSC Site with Media Conversion TDM – Ethernet

Interface modules are required to connect the site routers to a TDM based Backhaul
Network (serving Packet Abis over TDM BTSs). Recommended option in such a case is:
• CISCO 1-Port Channelized STM-1/OC-3 SPA [SPA-
1XCHSTM1/OC3] 3
SPA-1XCHSTM1/OC3 is a (single-height) Shared Port Adapter module that inserts into a
subslot of a compatible SIP carrier card to provide network connectivity and increased
interface port density.

http://www.cisco.com/en/US/prod/collateral/modules/ps6267/product_data_sheet0900aecd8
0350c53.html

Figure 14: CISCO 1-Port Channelized STM-1/OC-3 SPA

The following SIP carried cards are recommended to host the above SPA:
• CISCO 7600 Series SPA Interface Processor-200 [7600-SIP-
200]

SIP-200 is a carrier card that inserts into a router slot like a line card and contains subslots to
house one or more SPAs providing interface port(s) for network connectivity.
SIP-200 can host two SPA-1XCHSTM1/OC3 modules 3 in order to provide STM-1/OC-3
interface redundancy (via MSP/APS protocols).

3
SIP-200 supports up to 4 (single-height) SPAs.

DN0976623 © 2014 Nokia Networks 35 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

• CISCO CISCO 7600 Series SPA Interface Processor-400

[7600-SIP-400]
SIP-400 is equivalent to SIP-200 wrt SPA-1XCHSTM1/OC3 modules (difference between the
two resides in other features, e.g. SIP-400 can host GBE/10GE SPAs while SIP-200 can
host FE SPAs).

http://www.cisco.com/en/US/prod/collateral/routers/ps368/product_data_sheet0900aecd8027
c9df.html
http://www.cisco.com/en/US/prod/collateral/routers/ps368/product_data_sheet0900aecd8027
c9e6.html

Figure 15: CISCO SIP-200 and SIP-400

Besides the above recommended option for TDM interfaces, alternatives are also available
from CISCO but with some limitations in terms of supported features. A summary is provided
in the following table for comparison.

DN0976623 © 2014 Nokia Networks 36 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

Table 7: CISCO 7600 series routers – STM-1/OC-3 interface modules comparison

Long Name Product Name STM- Channeli PPP ML- Hosting Remarks
1/OC-3 zed PPP card
ports E1/T1

CISCO 1-Port SPA- 1/1 63/84 PPP ML- SIP200 Recommended option,
Channelized 1XCHSTM1/O PPP SIP400 supporting (among
STM-1/OC-3 C3 others): channelization,
Shared Port fractional E1/T1, ML-
Adapter PPP with up to 12
E1/T1 per bundle, up to
42 ML-PPP bundles per
SPA with at least 2
E1/T1 per bundle,
VC3/VC4/VC12 virtual
containers, ...

-
CISCO 2-Port SPA-2XOC3- 2/2 PPP SIP200 Does not support
OC-3c/STM-1c POS SIP400 channelization and ML-
POS Shared PPP.
Port Adapter

-
CISCO 4-Port SPA-4XOC3- 4/4 PPP SIP200 Does not support
OC-3c/STM-1c POS SIP400 channelization and ML-
POS Shared PPP.
Port Adapter

CISCO PA-MC-STM-1 1/- 63/- PPP ML- FlexWan Does not support OC-3
Multichannel MM PPP (STM-1 only). Requires
STM-1 Port Enhanced FlexWan.
PA-MC-STM-1
Adapter
SMI

-
CISCO 4-Port OSM-4OC3- 4/4 PPP - (stand- Does not support
OC-3c/STM-1c POS-SI+ alone channelization and ML-
(+ 4 GE
POS card) PPP. Not compatible
ports)
Enhanced with RSP720.
Optical
Services
Module

DN0976623 © 2014 Nokia Networks 37 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

-
CISCO 8-Port OSM-8OC3- 8/8 PPP - (stand- Does not support
OC-3c/STM-1c POS-SI+ alone channelization and ML-
(+ 4 GE
POS card) PPP. Not compatible
OSM-8OC3- ports)
Enhanced with RSP720.
POS-SL+
Optical
Services
Module

Worth noting that interface modules without support of channelization and ML-PPP can be
an option only in those deployment scenarios where a router (supporting such features) is
used as an aggregation point in the transport network close to the BTSs.

Recommended SFPs for STM-1/OC-3 SPA modules are:

• For CISCO 1-Port Channelized STM-1/OC-3 SPA [SPA-
1XCHSTM1/OC3]
o OC-3/STM-1 SFP, SM Fiber, Intermediate Reach (IR-1)
[SFP-OC3-IR1] 4

4
This SFP is also supported by the other interface modules listed in Table 5. Additional SFP variants
are available (covering from 2 km up to 80 km distance) such as: Multi-mode Short Reach (MMI),
Single-mode Short Reach (SR) and Single-mode Long Reach (LR-1 and LR-2).

4.2.7 Recommended System Configuration (7609)

For the deployment of an IP site solution for BSC with a redundant pair of Multi Layer (L2/L3)
Switches based on CISCO 7600 series devices, the installation can be based on the
following equipment configuration (product number in square brackets).

Table 8: CISCO 7600 Recommended Chassis and cards

Minimum configuration Optional/Alternative module

Chassis CISCO 7609-S Chassis
[CISCO7609-S]
IOS Advanced IP Services license
Software [IOS 12.2 (33) SRD4].
The SW release here indicated,
is an up-to-date example at the

DN0976623 © 2014 Nokia Networks 38 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

Minimum configuration Optional/Alternative module

time of writing the present
document. SW releases are
going to evolve according to
7600 roadmap.
Supervisor Card In case of Minimum In case higher capacity is
configuration, the following required (for example, routing
Supervisor card may be used tables) an enhanced version of
the supervisor (processor) card
7600 Router Switch Processor
3 is also available as an
720 [RSP720-3C-GE]
alternative:
7600 Router Switch Processor
720 high capacity [RSP720-
3CXL-GE]
Line cards In case only electrical GE As an alternative a WAN
interfaces are used, the interface line card may be used
following LAN interface line card (see 4.2.3).
is suggested:
In case SyncE is the chosen
Catalyst 6500 48-port synchronization solution for
10/100/1000 GbE Module, RJ- network synchronization, the
45 [WS-X6748-GE-TX] line card(s) are to be
mandatorily selected among the
ES+ units and variants (see
4.2.3).
In case a 10 GbE
interconnection between the two
routers is considered, the
following unit could be used for
cost-efficient implementation:
- Catalyst 6500 8-port
10 GbE module [WS-
X6708-10G-3C]
WS-X6708-10G-3C is less
applicable as Backhaul WAN
interface unit due to limitations
in queuing and shaping while
backbone ports usually do not
use shaping because it is not
reasonable to limit bandwidth
1
Product number for ordering 7609-S Chassis together with RSP720-3C-GE
processor is as follows [7609S-RSP720C-P].

DN0976623 © 2014 Nokia Networks 39 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

Default values in Error! Reference source not found.Table 7 are in line with
/E/.

4.2.8 Alternative System Configuration (7604)

CISCO 7604 is seen as Low End alternative in case a limited connectivity is

required, for example, single BSC, no RNC co-siting, etc.
This is a possible solution but not the recommended one due to the inherent
constraints in terms of future expansion (four slots only). However, it is
mentioned because some Operators might already have this equipment in
field.
The system configuration is the same as that in Error! Reference source not
found.Table 7 with the following difference in chassis.
• Chassis:
CISCO 7604 Chassis [CISCO7604] 6
Same SW version applies with the same Supervisor (processor) and Line
Cards are to be hosted in the 7604 Chassis with the restriction of four slots
instead of nine.

4.3 CISCO Management

In case of first installation, CISCO Switch/Router may be commissioned only
locally.
There are different ways for provisioning and monitoring CISCO 7600 and
CISCO Catalyst 3750 like for example:
• CLI commands via Telnet/SSH + additional tools from CISCO (for
example, CISCOWorks).

• SW packaged provided by EMC like for example:

o EMC Ionix SW package (Fault Management)
o EMC IT Performance Reporter SW package
(Performance Management).
Please note that FM “EMC Ionix” (formerly called smart) is integrated in
NetAct. Moreover, “EMC IT Performance Reporter” is planned to be integrated
in NetAct with full availability in Q2/Q3 2010.

DN0976623 © 2014 Nokia Networks 40 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION External L2/L3 equipment in bsc RG20(BSS) on top: CISCO
products

Note:
Please refer to official CISCO documentation for further
information on CISCO Management.

DN0976623 © 2014 Nokia Networks 41 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

5 BSC transport site solution: MLS Setup

5.1 Installation

5.1.1 BSC3i/FlexiBSC and TCSM3i

In BSC transport site solution two Multi Layer Site Switches (for example, two
CISCO 7609-S routers) provide site connectivity along with redundancy
protection.

Figure 16 shows how to connect MLSs to Backbone/Backhaul, BSC/TCSM,

ATS (Atrica A-2200), PTP-M (Symmetricom TP5000) and SGW (Juniper
Netscreen).

Note:
Port type and port density depends on type and number
of connected devices. Also throughput impacts the
number and type of port (see examples in BSC Transport
Site Solution Mother Document /A/ section 7.3).

Figure 17 is similar to
Figure 16, with the interfaces with Link aggregation highlighted.
The site solution can also be shared (not shown in the picture) with more than
one BSC and/or with additional network elements such as MGW, RNC.
BB (BackBone) and BH (BackHaul) ports are used for connecting to
transport Networks.
Both MLSs are connected to Backbone/Backhaul via dedicated ports (BB-00
and BH-00 in

DN0976623 © 2014 Nokia Networks 42 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Figure 16). One single GE is used in case of low throughput. Alternatively, 10

GE or Multiple GE interfaces with link aggregation helps in coping with high
traffic scenarios (Figure 17).

The same service characteristics will be provided to Backhaul port(s) in MLS-0

and in MLS-1.

IM (inter MLS) ports for MLS redundancy.

MLSs are interconnected via dedicated ports (IM-00, IM-01 port in
Figure 16). At least two interfaces in Link aggregation for redundancy
purposes are configured. As an alternative, more than two GE interfaces with
link aggregation or two 10 GE interfaces with link aggregation helps in coping
with high traffic scenarios.
BSx (BSC) ports for connection to BSC.
More than one BSC may be connected to MLSs depending on Site
configuration and port availability. BSx ports are used in connecting MLS to
BSCx.
TC (TCSM) ports for connection to TCSM.
More than one TCSM may be connected to MLSs depending on Site
configuration and port availability. TCx ports are used in connecting MLS to
TCSMx.
T (trusted) and U (untrusted) ports for connection to SGW.
Juniper Netscreen is the SGW recommended by Nokia for RG20(BSS) on top.
Active/active redundancy is suggested (two equipments SGW-0 and SGW-1).
One single GE may be used. 10 GE or Multiple GE interfaces with link
aggregation allows in coping with high traffic scenarios (Figure 17).
Tx refers to the so called trusted traffic including all traffic generated by
BSC/PTP-M/ATS towards SGW and vice versa.
Ux refers to the so called untrusted traffic including all traffic from
Backbone/Backhaul towards SGW and vice versa.
SP ports for connection to PTP-M (Symmetricom TP5000)
Symmetricom TP5000 is the PTP-M recommended by Nokia for RG20. SP
ports in MLS are used in connecting the symmetricom TP5000 (PTP-M
recommended solution). In the recommended configuration, IOC 1 is the
active card and up to two active links may be connected per card. IOC2 is for
redundancy.
One port is dedicated for Remote Management.
In principle more then one TP5000 device may be connected to MLS. The
number of equipment depends on the BTS to be synchronized via PTP 1588
(TP5000 supports 500BTS/active port i.e. 1000BTS/active IOC).

DN0976623 © 2014 Nokia Networks 43 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

AA ports for connection to ATS (ATRICA A-2000)

Atrica A-2200 is the ATS device recommended by Nokia for RG20. AAx ports
in MLS are used to connect the A-2200. Up to 8 Eth interfaces may be
configured. A-2200 redundancy aspects are described in /B/. Link aggregation
may be used as a sort of line redundancy.

Note:
In this document Backbone port is used for traffic towards
CN, NetAct and for in-band CISCO Management traffic.
Separated DCN is not considered.

DN0976623 © 2014 Nokia Networks 44 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

MLS-0
BSx-00 BSC
BSx-01
BSx-02
Backbone-0 BSx-03
SWU-0
BB-00
BSx-04
Backhaul-0 BSx-05
BH-00 SWU-1
BSx-06
BSx-07
BSx-08 SWU-2
BSx-09
BSx-10
BSx-11 SWU-3
BSx-12
SGW-0 (Netscreen) ETP-0
T-00 Tx-00
TCx-00 ETP-1
U-00 Ux-00 TCx-01
TCx-02
TCx-03 ETP-2
TCx-04
TCx-05
IMC SPx-00 IM-00 ETP-3
PTP-M (Tp5000) IM-01
SPx-01 ETP-4
IOC 1 SPx-02
ETP-5
SPx-01
IOC 2
SPx-02
IM-00
IM-01

ETP-6

ETP-7
BSx-00
SGW-1 (Netscreen) BSx-01
BSx-02 ...
T-00 Tx-00 BSx-03
BSx-04
U-00 Ux-00 BSx-05 ETP-9
BSx-06
BSx-07
BSx-08 TCSM
A-00 AAx-00 BSx-09
ATS (A-2200) BSx-10 ETP-0
A-01 AAx-01 BSx-11
BSx-12
ETP-1

Backhaul-1 ETP-2
TCx-00
BH-00
TCx-01
Backbone-1 TCx-02 ...
BB-00
TCx-03
TCx-04
Link Aggregation MLS-1 TCx-05 ETP-6

DN0976623 © 2014 Nokia Networks 45 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Note 1: In this picture ETP means generally ETIP, ETPE, ETPA

Note 2: A-2200 redundancy aspects are not included in this picture (see /B/)

Figure 16: MLS deployment reference model

DN0976623 © 2014 Nokia Networks 46 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Note 1: In this picture ETP means generally ETIP, ETPE, ETPA

Note 2: A-2200 redundancy aspects are not included in this picture (see /B/)

Figure 17: MLS reference model (with Link Aggregation at Backbone/Backhaul/SGW/ATS)

Port type is summarized in Error! Reference source not found.Table 9.

DN0976623 © 2014 Nokia Networks 47 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Table 9: MLS Port type/usage – FlexiBSC

Source Port ID Port type Usage

BB-00 GE or 10 GE or non Ethernet WAN Backbone traffic
BH-00 GE or 10 GE or non Ethernet WAN Backhaul traffic

IM-00, IM-01 GE or 10 GE Inter MLS traffic

BSx-00 10/100/1000 BaseT/TX/T or 1000 Base-SX BSC traffic (NetAct, CBC,

SIGTRAN, external ETPSIG,
(*)
PAoEth M/C-plane)
BSx-01 10/100/1000 BaseT/TX/T or 1000 Base-SX BSC traffic (GboIP)
(*)
BSx-02, … BSx-12 1000 BaseT or 1000 baseLX/SX BSC traffic (ETP)

TCx-00, … TCx-04 1000 BaseT or 1000 baseLX/SX TCSM traffic

SPx-00 10/100 BaseT/TX This port may be used for

remote TP5000 management.
SPx-01, … SPx-03 10/100/1000 BaseT/TX/T or 1000 BaseLX/SX S-plane (PTP packets)

AAx-00, … 10/100 BaseT/TX This port may be used for

remote A-2200 management.
AAx-01, … AAx-18 10/100/1000 BaseT/TX/T or 1000 Base-FX S-plane (Dummy PWE)

1000 BaseT or 1000 BaseLX/SX Trusted traffic to/from SGW

Tx-00, …
(Netscreen).

1000 BaseT or 1000 BaseLX/SX Untrusted traffic to/from SGW

Ux-00, …
(Netscreen).

(*) 10 Mbps to be used carefully in order to avoid bottlenecks.

5.1.2 Stand-alone mcBSC and mcTC

Figure 18 shows how to connect MLSs when stand-alone mcBSC and mcTC
are concerned (only one mcTC is shown for simplicity but more than one can
be deployed/used).

DN0976623 © 2014 Nokia Networks 48 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Note:

Port type and port density depends on type and number of connected
devices. Also throughput impacts the number and type of ports (see
examples in BSC Transport Site Solution Mother Document /A/ section
7.4).

7
10 Mbps to be used carefully in order to avoid bottlenecks.

BB (BackBone) and BH (BackHaul) ports for connection to transport

Networks.
See sub 5.1.1

IM (inter MLS) ports for MLS redundancy.

See sub 5.1.1

BSx ports for connection to mcBSC.

More than one BSC may be connected to MLSs depending on Site
configuration and port availability. BSx ports are used to connect MLS to
BSCx. BSx ports from MLS-0 are connected to mcBSC Module-2 whereas
BSx ports from MLS-1 are connected to mcBSC Module-1.

TC ports for connection to mcTC.

More than one TC may be connected to MLSs depending on Site
configuration and port availability. TCx ports are used to connect MLS to TCx.
TCx ports from MLS-0 and from MLS-1 are connected to the same mcTC
Module.

T (trusted) and U (untrusted) ports for connection to SGW.

See sub 5.1.1

SP ports for connection to PTP-M (Symmetricom TP5000)

See sub 5.1.1

AA ports for connection to ATS (ATRICA A-2000)

See sub 6.1.1.

DN0976623 © 2014 Nokia Networks 49 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Note 1: Only one mcTC is shown in this picture.

Note 2: A-2200 redundancy aspects are not included in this picture (see /B/)

Figure 18: MLS deployment reference model – Stand-alone mcBSC

DN0976623 © 2014 Nokia Networks 50 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Port type and usage is the same as in previous section (Table 9) with the exception of ports
towards mcBSC (BSx) and mcTC (TCx) as summarized in Table 10.

Table 10: MLS Port type/usage – Stand-alone mcBSC

Source Port ID Port type Usage

BSx-00 1000 Base-T or 1000 Base-LX/SX mcBSC traffic ([NetAct, CBC, GboIP,
SIGTRAN, external ETPSIG)

BSx-01, BSx-02 (BSx-03, 1000 Base-T or 1000 Base-LX/SX mcBSC traffic (Packet Ater or AoIP)
BS-04 as high traffic or 10G Base-LR/SR
options)

BSx-05, BSx-06 (BSx-07, 1000 Base-T or 1000 Base-LX/SX mcBSC traffic (Packet Abis)
BS-08 as high traffic or 10G Base-LR/SR
options)

(BSx-09 as integrated 1000 Base-T or 1000 Base-LX/SX mcBSC traffic (PTP or SyncE)
sync option)

TCx-00 1000 Base-T or 1000 Base-LX/SX mcTC traffic (Remote MMI, NTP)

TCx-01 1000 Base-T or 1000 Base-LX/SX mcTC traffic (Packet Ater, ETPSIG)

TCx-02 1000 Base-T or 1000 Base-LX/SX mcTC traffic (Packet Ater, ETPSIG)

(TCx-03 as integrated 1000 Base-T or 1000 Base-LX/SX mcTC traffic (PTP or SyncE)
sync option)

All other ports See Table 7 See Table 7

DN0976623 © 2014 Nokia Networks 51 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

5.2 Provisioning overview

Note:
This section provides an overview of key issues to be
considered when setting MLSs in a BSC Site. This section
does not describe commands to be used while configuring
MLSs. It is expected that reader knows CISCO 7600
products, but he/she needs an overview of main concepts
of Nokia GSM RAN.

CISCO 7609 is a multilayer switch i.e. one single physical device that includes switching as
well as routing functionalities. Switch Virtual Interface (SVI) is the interface between “internal
Router” and ”Internal Switch”. An IP address is assigned to each SVI.

Provisioning of CISCO 7609 includes the following steps (order is only for readability
purpose, it does not provide the exact sequence of steps):
• L2&L3 ports setting
• VLAN& Subnet setting
• MTU size
• Link aggregation
• HSRP and Default Gateway setting
• IGP setting
• Multiple Spanning Tree Protocol (MSTP)
• SyncE setting (optional)
• ETH-OAM setting (optional)
• QoS
Examples of configurations are depicted in the sections 5.3, 5.3.2 and 5.3.3. Recommended
external equipments are considered i.e.:
• Symmetricom TP5000 PTP 1588 Master Clock (see /B/)
• ATRICA A-2200 for Dummy PWE generation (see /B/)
• Juniper Netscreen Security GW&Firewall (see /C/)

DN0976623 © 2014 Nokia Networks 52 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

5.2.1 L2&L3 ports setting

Ports connected to FlexiBSC SWUs are L3 type. It means that MLS expects
on this port a next hop router (MLSs see SWUs as next hop routers).
Ports connected to FlexiBSC ETPs are instead L2 type.
Ports connected to mcBSC Module-1 and Module-2 Switch are L2 type.
Ports connected to Backbone are L3 type.
Backhaul ports are L2 or L3 depending on Network type. Ports connected to
Sync Devices and SGW are L2 type.
Ports used for inter MLS connection are L2 type.
Examples in section 6.3 and 6.4 for FlexiBSC and mcBSC respectively.

5.2.2 VLAN & SubNet setting

IP endpoints of devices/units connected to MLSs via L2 ports (e.g.

Synchronization devices, FlexiBSC ETPs, mcBSC units) are organized in
Subnets. Subnet and associated VLAN have to be provided to MLS.
More than one Subnet may be defined depending on scenario and operator
choices.
Examples in section 6.3 and 6.4 for FlexiBSC and mcBSC respectively.

5.2.3 MTU size

MTU size of 1500 bytes is configured on all site routers interfaces that are
connected to the BSC or the mobile backhaul network. It is assumed that the
network supports the MTU of at least 1500 bytes end-to-end.
BTS requires that in case of IPSEC enable, inner IP packet M/C/U/S-plane is
not fragmented by IPSEC. In Juniper SGW this is not a problem since there is
a parameter to disable the inner fragmentation.

5.2.4 Link aggregation

One single GE is used in case of low throughput. Alternatively, 10 GE or

Multiple GE interfaces with link aggregation allows in coping with high traffic
scenarios (for example Figure 17 and Figure 18).
CISCO Supports:
• CISCO-proprietary Port Aggregation Control Protocol (PAgP) or

DN0976623 © 2014 Nokia Networks 53 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

• Link Aggregation Control Protocol (LACP) defined in IEEE 802.3ad

CISCO proprietary PAgPP can be used between MLSs and in general
between MLS interface and any other CISCO product with which it interfaces.
Standard LACP is to be used on other cases for example, with Juniper SGW
(also with ATRICA as in /B/).

5.2.5 HSRP and Default Gateway setting

MLSs are interconnected and HSRP protocol between MLS allows MLSs to
appear to the hosts as a single router. This means that MLSs acts as Virtual
GW.
Virtual IP address is used as Default Gateway in BSC (ETP) and in synch
devices.
ETPs send ARP packets to the virtual router using Virtual IP address.
Thereafter, Virtual MAC Address is provided to the host. Virtual MAC address
is used in sending packets.

Initially, the selection of the active and standby routers is based on priority.
When comparing priorities of two different routers, the router with the
numerically higher priority wins. In the case of routers with equal priority, the
router with the higher IP address wins.

The following timer settings are recommended:

• HSRP hello timer: 300 ms
• HSRP hold timer: 1000 ms
However, lower values need to be defined in order to optimize the HSRP
behaviour for Packet Abis, first recommendation (to be eventually confirmed
after testing) is:
• HSRP hello timer: 150 ms
• HSRP hold timer: 500 ms

HSRP track uplink is also recommended.

HSRPv2 may allow an easier setup because a one to one mapping between
VLAN and HSRP group ids can be used. With HSRPv1 Group numbers are
restricted to the range between 0 and 255. HSRP version 2 expands the group
number range from 0 to 4095. HSRPv2 is not mandatory, since it is possible to
group more than one VLAN on one single HSRP group.
Additionally, in case there is a high number of HSRP group to be created, the
feature "multiple HSRP group optimization" can be used to reduce the
computational load. This feature allows selecting one HSRP group on a

DN0976623 © 2014 Nokia Networks 54 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

physical interface for the purposes of electing active and standby routers as a
master group. Other HSRP groups may be created on each sub interface as
slave groups and linked to the master group via the group name. The slave
groups will follow the master group.
For commands and examples please look at CISCO documentation through
the following links:
HSRP:
http://www.cisco.com/en/US/docs/internetworking/case/studies/cs009.html
HSRPv2:
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gthsrpv2.htm
l
multiple HSRP group optimization:
http://www.Cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a
0080094e8c.shtml
Examples in section 6.3 and 6.4 for FlexiBSC and mcBSC respectively.

5.2.6 IGP setting

OSPF is an interior gateway protocol that routes Internet Protocol (IP)

packets. Via OSPF, a router gathers link state information from available
routers and constructs a topology map of the network. The topology
determines the routing table.
OSPF detects changes in the topology, such as link failures, very quickly and
converges on a new loop-free routing structure within seconds. It computes
the shortest path tree for each route using a method based on Dijkstra's
algorithm, a shortest path first algorithm.
More in general IGP (Interior Gateway Protocol) refer to a set of routing
protocols such as:
• Routing Information Protocol (RIP)
• Interior Gateway Routing Protocol (IGRP)
• Enhanced Interior Gateway Routing Protocol (EIGRP)s
• Open Shortest Path First (OSPF)
• Intermediate system to intermediate system (IS-IS)

IGP protocol (for example, OSFP or IS-IS) has to be configured on

Backbone/Backhaul if L3 based, the protocols depend on Transport Network.

Routing between MLS and SWUs is done by using:

• Static Routing or

DN0976623 © 2014 Nokia Networks 55 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

• Dynamic Routing.
SWU supports OSPF and in this way BSC may provide an automatic way to
inform its Subnets like for example, O&M, SIGTRAN-1, SIGTRAN-2, Gb,
OMUSIG, TRXSIG and ext ETPSIG subnets.

MLSs redistribute BSC Networks and advertise ETP/Synchronization SubNets

to other routers in the Network.

When OSPF is used (Routing ID == Loopback) Loopback interface setting is

recommended.

In case of IPSEC, OSPF has to be enable also towards Juniper Security

Gateway.

5.2.7 Multiple Spanning Tree Protocol (MSTP)

(Rapid) Spanning Tree Protocol (RSTP), as the name suggests, creates a

spanning tree within a mesh network of connected layer-2 bridges and
disables those links that are not part of the tree, leaving a single active path
between any two network nodes.
The Multiple Spanning Tree Protocol (MSTP) configures a separate Spanning
Tree for each VLAN group and blocks all but one of the possible alternate
paths within each Spanning Tree (Error! Reference source not found.Figure
19).

If the Transport Network is L2 (typically Backhaul), Multiple Spanning Tree

protocol has to be configured in MLSs.
For Instance in RG20(BSS) on top, in case of Packet Abis and/or AoIP,
connectivity between MLSs and SWU is L3. L2 connectivity between SWUs
and MLS is not considered in this document.

DN0976623 © 2014 Nokia Networks 56 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

MLS/Router

Fastport
Packet Abis over TDM

BSC

ETP

ETPs not
involved in
MSTP

VLAN #a
MLS/Router

Figure 19: MSTP in BSC Transport Site Solution (L2 Backhaul, L3 connectivity between SWU
and MLS)

CISCO Portfast concept allows an interface to be configured as a Layer 2

access port. This helps in immediate transition from blocking state to
forwarding state. In other cases, such ports participate in all STP port state
changes.
CISCO Portfast is recommended to be applied at MLS ports connected to
ETPs and to Sync Devices.

5.2.8 Ethernet OAM setting

Ethernet OAM can be configured only in case of L2 Backhaul.

There are different Ethernet OAM mechanisms defined in ITU-T Y7131,
802.1ah etc.

Service Layer Ethernet OAM supported by RG20 BTS are (Error! Reference
source not found.Figure 20):
• Unicast Service Layer Ethernet Loopback (ETH-LB) in accordance
with ITU-T Y.1731
• On demand (Single Ended) Frame Loss Measurement (ETH-LM) -
Y.1731

DN0976623 © 2014 Nokia Networks 57 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

BSC, Juniper Netscreen, Symmetricom TP5000 do not support ETH-OAM.

ATRICA A-2200 supports both procedures. CISCO 7600 supports ETH-LB
only. It is expected that ETH-LB is terminated by MLSs.

BSC Site
BSC
TCSM

DCN/BackBone Network
L3 SGW

MLS SGW

OAM
La yer Eth
ce
Servi
ATS
MLS
AM
ayer Eth O
Service L
SSM
(*)
PTP-M
Backhaul Network
SSE L2
Equipment

Figure 20: Ethernet OAM Concept for RG20(BSS) on top

CISCO OAM features:

Supported Y.1731 functions are described in CISCO documentation at the

following link:
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps8802/ps6970/ps1838/pr
od_bulletin0900aecd805ddce3.html#wp9001527

DN0976623 © 2014 Nokia Solutions and Networks 58 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

5.2.9 SyncE setting

The Synchronous Ethernet (SyncE) method refers to a master-slave method

using an Ethernet physical layer.
The main disadvantage from SyncE is that a specific type of HW is needed at
the Ethernet interfaces for extracting the timing information from the Rx side
and to transmit it at the Tx side.
When SyncE is used as the synchronization method it has to be taken into
account that all intermediate nodes in the network up to the PRC should also
support SyncE. However, that does not mean that all Eth connection in all
ports have to carry SyncE.

If some of the BTSs are synchronized via SyncE, Backhaul port BH-00 has to
be provisioned in an ES+ line card and SyncE Master (for example FlexiBSC
ETP) has to be connected to ES+. It is not mandatorily required that other
interfaces connected to ES+ should support SyncE at the physical Layer.
Configuration of SyncE for CISCO 7600 series is described in CISCO
documentation available at the following link:
https://www.cisco.com/en/US/docs/routers/7600/install_config/ES40_config_guide/es4
0_config_guide.pdf

5.2.10 Quality of Service (QoS)

5.2.10.1 L3

5.2.10.2 Packet marking in BSC/PTP-M/ATS

The BSC/PTP-M/ATS provides packet priority marking on the basis of
differentiated services code point (DSCP) as shown:
• In case of PWE Ater and PWE A (FlexiBSC only), DSCP is
configurable per PW.
• In case of PWE Abis (FlexiBSC only), DSCP is configurable per
PW and within the PW all traffic is mapped to a single PHB (see
Error! Reference source not found.Table 9 for range and
default values).

• In case of AoIP, DSCP field is configurable per Traffic Class (see

Error! Reference source not found.Table 9 for range and
default values).

DN0976623 © 2014 Nokia Networks 59 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

• In case of Packet Abis, DSCP field is configurable as per Traffic

Class (see Error! Reference source not found.Table 9 for
range and default values).

• In case of Packet Ater (mcBSC only), DSCP field is configurable

as per CS Traffic Class (see Table 9 for range and default value).

Table 11: DSCP marking

Interface Traffic Class DSCP Range DSCP Default

PWE Abis All BTS traffic EF, BE BE (000000 bin, 0 dec)
CS BE, EF, AF11, AF21, AF31, AF41 AF41 (100010 bin, 34 dec)
PS BE, EF, AF11, AF21, AF31, AF41 AF31 (011010 bin, 26 dec)
Packet Abis Clock Synch BE, EF, AF11, AF21, AF31, AF41 EF (101110 bin, 46 dec)
C-plane BE, EF, AF11, AF21, AF31, AF41 EF (101110 bin, 46 dec)
M-plane BE, EF, AF11, AF21, AF31, AF41 BE (000000 bin, 0 dec)
CS BE, EF, AF11, AF21, AF31, AF41 AF41 (100010 bin, 34 dec)
AoIP External ETPSIG BE, EF, AF11, AF21, AF31, AF41 EF (101110 bin, 46 dec)
Clock Synch BE, EF, AF11, AF21, AF31, AF41 EF (101110 bin, 46 dec)

Remark: "Clock Synchronization via Empty Dummy PW" (used for ACR with
BTS in Packet Abis mode) follows the same DSCP marking rule as Packet Abis
Clock Synchronization ToP.

Default values in Table 11 are in line with SFS /D/.

5.2.10.3 Packet classification/handling in Multilayer Switches

The classification/handling of the ingress packets in the MultiLayer Site
Switches is based on the received DSCP in the Ethernet ports connected to
the BSC units.

Diffserv configuration (DSCP setting) has to be preserved by the site

equipment.
Overruling of BSC Diffserv setting is possible in the MultiLayer Site Switches
but it is not recommended.

All cards support at least some kind of classification (for details please refer to
CISCO documentation). Let us consider for example, Ethernet line card in the

DN0976623 © 2014 Nokia Networks 60 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

site equipment supporting only four queues (which is a common bottom value
for transmission devices), the mapping indicated in the Error! Reference
source not found.Table 10 should be applied.

Table 12: Site equipment queue mapping (example, 4 queues)

DSCP PHB Tx queue in site equipment

EF 1st priority queue (highest)
AF4 2nd priority queue
AF3, AF2, AF1 3rd priority queue
BE 4th priority queue (lowest)

An example of configuration to cope with the expected behaviour depicted in

Error! Reference source not found.Table 10 is summarized as follows:
• Strict priority for 1st priority queue
• WRR (Weighted Round Robin) or DWRR (Deficit Weighted Round
Robin) for other queues. Weights (i.e. percentage of bandwidth
allocated to each queue) can be exploited as suggested in Table
13.

Table 13: Site equipment queue mapping (example, 4 queues)

DSCP PHB Tx queue in site equipment

EF strict priority queue
AF4 standard queue (higher weight)
AF3, AF2, AF1 standard queue (intermediate weight)
BE standard queue (lowest weight)

5.2.10.4 L2

5.2.10.5 VLAN priority p-bits marking in BSC/PTP-M/ATS

In case of PWE Abis VLAN priority is configurable per PW. Default VLAN
priority is 7.

DN0976623 © 2014 Nokia Networks 61 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

In case of Packet Abis, setting of VLAN priority (p-bits) is derived from DSCP
setting via configurable mapping (see Error! Reference source not
found.Table 12 for range and default values).
Remark: "Clock Synchronization Empty Dummy PW" (used for ACR with BTS
in Packet Abis mode) follows the same p-bits marking rule as Packet Abis
Clock Synchronization ToP.

Table 14: Packet Abis (mapping between DSCP PHB and VLAN priority)

DSCP PHB VLAN priority range VLAN priority default

BE 0-7 0
AF1 0-7 1
AF2 0-7 3
AF3 0-7 4
AF4 0-7 5
EF 0-7 6

Default values in Table 14 are in line with /D/.

5.2.10.6 VLAN priority p-bits handling in MLSs

VLAN priority marking has to be preserved by the site equipment.
In case VLAN priority marking is done by the MLSs (for example, PAoEth
C/M-plane with Backhaul L2), it has to be derived from DSCP mappings as
reported in Error! Reference source not found.Table 12.
Hence CISCO default mapping cannot be used and appropriate configuration
has to be provided.

5.3 Provisioning examples BSC3i/FlexiBSC

5.3.1 Reference scenario #1 (Backbone/Backhaul L3)

5.3.1.1 Overview
The so called Reference scenario#1 (Backbone L3 + Backhaul L3) is
described in BSC Transport Site Solution Mother Document /A/.

DN0976623 © 2014 Nokia Networks 62 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

shows an example of MLSs connected to one BSC, one TP5000 and one A-
2200. MLS is composed by two main functionalities as depicted in the picture
(Switching + Routing functions):
• MLSs see SWUs as next hop routers.
• ETP IP endpoints for AoIP or PWE Ater belong to BSC-SITE-BB
Subnet.
• ETP IP endpoints for PAoEth U/S-plane and PWE Abis belong to
BSC-SITE-BH Subnet.
• SVI-1, SVI-3 are defined in MLS-0.
• SVI-2, SVI-4 are defined in MLS-1.
• TP5000 and A-2200 Setup are described in /B/.

Note:
In this example, next hop router SubNet /30 is used.
In the other cases the right dimension of Subnet depends
on the network configuration. In this example /24 subnet
is used for readability purposes.
It is also possible to split BSC-SITE-BH in different
subnets (one for Synch Device Endpoints and another
one for BSC Packet Abis U-plane and PWE Abis
endpoints).
In case if more than one BSC is present in the Site, it is
suggested to define a dedicated BSC-SITE-BB Subnet
and a dedicated BSC-SITE-BH Subnet per BSC.

DN0976623 © 2014 Nokia Networks 63 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

MLS-0 BSC #1
SWU-0
a.b.1.1/30 a.b.1.5/30 a.b.1.6/30
Backbone-0 BS1-00
BB-00
Backhaul-0 BS1-01
BH-00 a.b.1.9/30 a.b.1.10/30
a.b.1.25/30
SWU-2

a.b.9.7
IP address belonging to

a.b.2.2
.3.2
BSC-SITE-BB Subnet

a.b
a.b.2.0/24
a.b.9.7

SVI-3

SVI-1
IP address belonging to
BSC-SITE-BH Subnet
a.b.3.0/24
a.b.9.7

BS1-02 ETP-0
IMC a.b.2.6 SP-00
a.b.2.4
a.b.9.7
SP-01
BS1-04
PTP-M (Tp5000) SP-02
ETP-1
IOC 1 a.b.2.5
a.b.3.6

a.b.3.7

Virtual@
a.b.3.1

a.b.2.1
9.1
HSRP

IOC 2 ETP-2
a.b.9.7
a.b.3.4

SP-01
SP-02
ETP-3
BS1-02 a.b.3.5
a.b.9.7
AA-00
BS1-04
AA-01
ATS (A-2200) AA-02
a.b.2.7
a.b.9.7
a.b.9.7
a.b.2.3

a.b.3.8
a.b.9.7
b.3.3

a.b.9.7
a.b.3.9
a.S VI-4

S VI-2

SWU-1

a.b.1.29/30 a.b.1.17/30 a.b.1.18/30

Backhaul-1 BS1-00
BH-00
Backbone-1
BB-00 BS1-01
a.b.1.13/30 a.b.1.21/30 a.b.1.22/30
MLS-1 SWU-3

Note 1: In this picture ETP means generally ETIP, ETPE, ETPA

Note 2: A-2200 redundancy aspects are not included in this picture (see /B/)

DN0976623 © 2014 Nokia Solutions and Networks 64 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Figure 21: Example of MLS configuration (Backbone L3 and Backhaul L3)

5.3.1.2 L3 ports provisioning

L3 ports provisioning is summarized in Table 15. Link aggregation is not
considered in the table.

Table 15: L3 port provisioning (reference scenario #1)

Next hop
MLS ID Port ID IP address Subnet Usage
unit
MLS-0 BB-00 Edge Router a.b.1.1 a.b.1.0/30 Backbone interface
BS1-00 SWU-0 a.b.1.5 a.b.1.4/30 O&M, CBC, SIGTRAN
based interfaces (A,
Lb, BBI, VNP),
PAoEc/m, external
ETPSIG
BS1-01 SWU-2 a.b.1.9 a.b.1.8/30 GboIP interface
MLS-1 BB-00 Edge Router a.b.1.13 a.b.1.12/30 Backbone interface
BS1-00 SWU-1 a.b.1.17 a.b.1.16/30 O&M, CBC, SIGTRAN
based interfaces (A,
Lb, BBI, VNP),
PAoEth c/m, external
ETPSIG
BS1-00 SWU-3 a.b.1.21 a.b.1.20/30 GboIP interface

MLS-0 BH-00 Edge Router a.b.1.25 a.b.1.24/30 Backhaul interface

MLS-1 BH-00 Edge Router a.b.1.29 a.b.1.28/30 Backhaul interface

5.3.1.3 VLAN & Subnet provisioning

In this example ETP and Synch Devices endpoints are organized in
SubNet/VLAN as summarized in Error! Reference source not found.Table
14.

DN0976623 © 2014 Nokia Networks 65 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Table 16: VLANs/Subnet provisioning (reference scenario #1)

VLAN/Subnet
VLAN ID Subnet Endpoints in the Subnet
Nickname
BSC-SITE-BB 20 a.b.2.0/24 AoIP IP endpoints
PWE Ater IP endpoints,
Synch Device Management IP endpoints
BSC-SITE-BB 30 a.b.3.0/24 BSC PAoEth U endpoints,
PWE Abis IP endpoints
Synch Device S-plane IP endpoints

Table 17: SVI (reference scenario #1)

VLAN IP Subnet
MLS ID SVI ID IP address Usage
ID
MLS-0 SVI-1 20 a.b.2.2 a.b.2.0/24 AoIP, PWE Ater, Synch Device
Management
MLS-0 SVI-2 30 a.b.3.2 a.b.3.0/24 PWE Abis, PAoEth U, Synch Device S-
plane

MLS-1 SVI-3 20 a.b.2.3 a.b.2.0/24 AoIP, PWE Ater, Synch Device

Management
MLS-1 SVI-4 30 a.b.3.3 a.b.3.0/24 PWE Abis, PAoEth U, Synch Device S-
plane

5.3.1.4 L2 port provisioning

Table 18: L2 port provisioning (Flexi BSC; reference scenario #1)

MLS ID Port ID Next hop unit Usage

MLS-0 BS1-02 ETP Host AoIP (TC in MGW) or PWE Ater
BS1-04 ETP Host Packet Abis or PWE Abis

SP-00 PTP-M Host PTP-M Management

SP-01 PTP-M Host S-plane (PTP messages)
SP-02 PTP-M Host S-plane (PTP messages)

DN0976623 © 2014 Nokia Networks 66 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

MLS ID Port ID Next hop unit Usage

IM-00 & MLS-1 Trunk Inter MLS connection

IM-01
(Link Agg)

BS1-02 ETP Host AoIP (TC in MGW) or PWE Ater

MLS-1 BS1-04 ETP Host Packet Abis or PWE Abis

SP-01 PTP-M Host S-plane (PTP messages)

SP-02 PTP-M Host S-plane (PTP messages)

AA-00 ATS Host ATS Management

AA-01 ATS Host S-plane (Dummy PWE)
AA-02 ATS Host S-plane (Dummy PWE)

IM-00 & MLS-0 Trunk Inter MLS connection

IM-01
(Link Agg)

5.3.1.5 HSRP provisioning

The overview is available in section 5.2.5. In this example:
• MLS-0 is the master for AoIP/PWE Ater traffic.
• MLS-1 is the master for Abis traffic.

Table 19: HSRP configuration (FlexiBSC;reference scenario #1)

HSRP
VLAN MLS VLAN IP
address
Group prio Group
Virtual router IP
ID
20 MLS-0 a.b.2.2 110 20 a.b.2.1
MLS-1 a.b.2.3 90
30 MLS-0 a.b.3.2 90 30 a.b.3.1
MLS-1 a.b.3.3 110

DN0976623 © 2014 Nokia Networks 67 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

5.3.2 Reference scenario #2 (Backbone L3 + Backhaul L2)

5.3.2.1 Overview
The so called Reference scenario#2 (Backbone L3 + Backhaul L2) is described in BSC
Transport Site Solution Mother Document /A/.
Error! Reference source not found.Figure 22 shows an example of MLSs
connected to one BSC, one TP5000 and one A-2200. MLS is composed of
two main functionalities as depicted in the picture (Switching + Routing
functions):
• MLSs see SWUs as next hop routers.
• ETP IP endpoints for AoIP or PWE Ater belong to BSC-SITE-BB
Subnet.
• BTS are grouped in N groups. Separated VLAN for M-plane is
used in this example. (In the picture N=2 i.e. two groups). Only
Packet Abis over Ethernet is considered in this example. M-plane
separation is not possible with PWE Abis.
• BTS C/U/S-plane IP endpoints, ETP IP endpoints and Synch IP
endpoints belong to Abis-U/S-1 , …, Abis-U/S-N Subnet.
N=2 in this example. Max 60 Abis-U/S VLAN are available per
BSC.
Please note that TP5000 supports up to 16 VLAN in the 2.0
release. If more than 16 VLAN are needed, it is suggested to
create an ad hoc subnet for Synchronization IP endpoints, then
PTP traffic will be routed and not switched by MLS.
• BTS M-plane IP endpoints belong to Abis-M-1, …, Abis-M-N.
N=2 in this example. Max 60 Abis-M VLAN are available per BSC.
• SVI-1, SVI-3, SVI-5, SVI-7, SVI-9 are defined in MLS-0.
• SVI-2, SVI-4, SVI-6, SVI-8, SVI-10 are defined in MLS-1.
• TP5000 and A-2200 Setup are described in /B/.

DN0976623 © 2014 Nokia Networks 68 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Note:
In this example, next hop router SubNet /30 is used.
In the other cases, the right dimension of Subnet depends
on the network configuration. In this example /24 subnet
is used for readability purposes.
In case if more than one BSC is present in the Site, it is
suggested to define a dedicated BSC-SITE-BB Subnet
per BSC.

DN0976623 © 2014 Nokia Networks 69 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

MLS-0 BSC #1
SWU-0
a.b.1.5/30 a.b.1.6/30
Backbone-0 a.b.1.1/30 BS1-00
BB-00
BS1-01
a.b.1.9/30 a.b.1.10/30
SWU-2

a.b.9.7 SVI-3
4.2 SVI-5
a.b.9.7 SVI-7

a.b.6.2 SVI-9
a.b.2.2 SVI-1
a.b.9.7
a.b.3.2

a.b.5.2
Backhaul-0
a.b.
BH-00
BS1-02 ETP-0
a.b.2.6 SP-00 BS1-04 a.b.2.4
a.b.9.7
IMC
SP-01
ETP-1
SP-02
PTP-M (Tp5000) a.b.2.5
a.b.9.7
IOC 1
a.b.6.6
a.b.5.6
a.b.6.7
a.b.5.7

Virtual@
HSRP
a.b.3.1

a.b.5.1
a.b.6.1

.b.9.1
a.b.4.1

a.b.2

IOC 2 ETP-2
a.b.6.4
a.b.9.7 a.b.5.4

SP-01
SP-02 ETP-3
Backhaul-1 BH-00 a.b.6.5
a.b.9.7 a.b.5.5
BS1-02
AA-00
BS1-04
AA-01
ATS (A-2200) AA-02
a.b.2.7
a.b.9.7
a.b.9.7
a.b.9.7
a.b.3.3
.4.3

a.b.2.3

a.b.5.8
a.b.9.7 a.b.6.8
a.b.9.7
SVI-8 a.b.5.3

SVI-10 a.b.6.3
SVI-6 a.b

a.b.5.9
a.b.9.7 a.b.6.9
a.b.9.7
SVI-4

SVI-2

SWU-1

a.b.1.17/30 a.b.1.18/30
a.b.1.13/30 BS1-00
Backbone-1
BB-00
BS1-01
a.b.1.21/30 a.b.1.22/30
MLS-1 SWU-3

Note 1: In this picture ETP means generally ETIP, ETPE, ETPA

Note 2: A-2200 redundancy aspects are not included in this picture (see /B/)

DN0976623 © 2014 Nokia Solutions and Networks 70 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Figure 22: Example of MLS configuration (Backbone L3 and Backhaul L2)

5.3.2.2 L3 ports provisioning

L3 ports provisioning is summarized in Error! Reference source not
found.Table 18 (Link aggregation is not considered).

Table 20: L3 port provisioning (FlexiBSC; network scenario #2)

Next hop
MLS ID Port ID IP address Subnet Usage
unit
MLS-0 BB-00 Edge a.b.1.1 a.b.1.0/30 Backbone interface
Router

BS1-00 SWU-0 a.b.1.5 a.b.1.4/30 O&M, CBC, SIGTRAN

based interfaces (A,
Lb, BBI, VNP),
PAoEc/m, external
ETPSIG
BS1-01 SWU-2 a.b.1.9 a.b.1.8/30 GboIP interface
MLS-1 BB-00 Edge a.b.1.13 a.b.1.12/3 Backbone interface
Router 0

BS1-00 SWU-1 a.b.1.17 a.b.1.16/3 O&M, CBC, SIGTRAN

0 based interfaces (A,
Lb, BBI, VNP),
PAoEth c/m, external
ETPSIG
BS1-01 SWU-3 a.b.1.21 a.b.1.20/3 GboIP interface
0

5.3.2.3 VLAN& Subnet provisioning

In this example ETP and Synch Devices endpoints are organized in
SubNet/VLAN as summarized in Error! Reference source not found.Table
19.

DN0976623 © 2014 Nokia Networks 71 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Table 21: VLANs/Subnet provisioning (FlexiBSC; network scenario #2)

VLAN/Subnet
VLAN ID Subnet Endpoints
Nickname
BSC-SITE-BB 21 a.b.2.0/24 AoIP endpoints,
PWE Ater endpoints,
Synch Device Management
Abis-M-1 31 a.b.3.0/24 BTS PAoEth M-plane endpoints
Abis-M-2 32 a.b.4.0/24 BTS PAoEth M-plane endpoints
Abis-U/S-1 91 a.b.5.0/24 BSC PAoEth U-plane endpoints,
PWE Abis endpoints,
Synch Device S-plane endpoints
Abis-U/S-2 92 a.b.6.0/24 BSC PAoEth U-plane endpoints,
PWE Abis endpoints
Synch Device S-plane endpoints

Table 22: SVI (network scenario #2)

VLAN IP Subnet
MLS ID SVI ID IP address
ID
MLS-0 SVI-1 21 a.b.2.2 a.b.2.0/xx
MLS-0 SVI-3 31 a.b.3.2 a.b.3.0/xx
MLS-0 SVI-5 32 a.b.4.2 a.b.4.0/xx
MLS-0 SVI-7 91 a.b.5.2 a.b.5.0/xx
MLS-0 SVI-9 92 a.b.6.2 a.b.6.0/xx

MLS-1 SVI-2 21 a.b.2.3 a.b.2.0/xx

MLS-1 SVI-4 31 a.b.3.3 a.b.3.0/xx
MLS-1 SVI-6 32 a.b.4.3 a.b.4.0/xx
MLS-1 SVI-8 91 a.b.5.3 a.b.5.0/xx
MLS-1 SVI-10 92 a.b.6.3 a.b.6.0/xx

DN0976623 © 2014 Nokia Networks 72 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

5.3.2.4 L2 port provisioning

L2 ports provisioning is summarized in Error! Reference source not
found.Table 21.

Table 23: L2 port provisioning (FlexiBSC; network scenario #2)

Next hop Spanning tree

MLS ID Port ID Usage
unit
MLS-0 BH-00 Edge Switch MSTP Backhaul traffic

MLS-0 BS1-02 ETP Portfast AoIP (TC in MGW) or PWE Ater

MLS-0 BS1-04 ETP Portfast Packet Abis

MLS-0 SP-00 PTP-M Portfast PTP-M Management

MLS-0 SP-01 PTP-M Portfast S-plane (PTP messages)
MLS-0 SP-02 PTP-M Portfast S-plane (PTP messages)

MLS-0 IM-00 & MLS-1 MSTP Inter MLS connection

IM-01
(Link Agg)

MLS-1 BH-00 Edge Switch MSTP Backhaul traffic

MLS-1 BS1-02 ETP Portfast AoIP (TC in MGW) or PWE Ater

MLS-1 BS1-04 ETP Portfast Packet Abis

MLS-1 SP-01 PTP-M Portfast S-plane (PTP messages)

MLS-1 SP-02 PTP-M Portfast S-plane (PTP messages)

MLS-1 AA-00 ATS Portfast ATS Management

MLS-1 AA-01 ATS Portfast S-plane (Dummy PWE)
MLS-1 AA-02 ATS Portfast S-plane (Dummy PWE)

DN0976623 © 2014 Nokia Networks 73 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Next hop Spanning tree

MLS ID Port ID Usage
unit
MLS-1 IM-00 & MLS-0 MSTP Inter MLS connection
IM-01
(Link Agg)

5.3.2.5 HSRP provisioning

The overview is available in section 5.2.5. In this example:
• MLS-0 is the master for AoIP/PWE Ater traffic.
• MLS-1 is the master for Abis traffic.

Table 24: HSRP configuration (FlexiBSC; network scenario #2)

HSRP
MLS Group prio
VLAN IP address Group ID Virtual router IP

21 MLS-0 a.b.2.2 110 21 a.b.2.1

MLS-1 a.b.2.3 90
31 MLS-0 a.b.3.2 90 31 a.b.3.1
MLS-1 a.b.3.3 110
32 MLS-0 a.b.4.2 90 32 a.b.4.1
MLS-1 a.b.4.3 110
91 MLS-0 a.b.5.2 90 91 a.b.5.1
MLS-1 a.b.5.3 110
92 MLS-0 a.b.6.2 90 92 a.b.6.1
MLS-1 a.b.6.3 110

DN0976623 © 2014 Nokia Networks 74 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

5.3.3 Reference scenario with IPSEC

5.3.3.1 Overview
The reference scenario with IPSEC is described in BSC Transport Site
Solution Mother Doc /A/.
Idea is to split traffic as summarized in Error! Reference source not
found.Figure 23.

MLS-0
BackBone#0 BSC
BackHaul#0
Traffic group#0:
•NetAct/CBC
•SIGTRAN-1
•AoIP
•PWE Ater
SWU-2 SWU-0
SGW-0
CPU
PCU
O&M

Untrusted traffic SIGTRAN-1

PTP-M
Gb SIGTRAN-2
Trusted traffic Subnet
ETP OMUSIG

TRXSIG
ATS
Traffic group#1: ETPSIG-c
•GboIP ETPSIG-m
•SIGTRAN-2 SGW-1
•ETPSIG
•PWE Abis
•Packet Abis

SWU-3 SWU-1
BackBone#1

BackHaul#1
MLS-1

Figure 23: IPSEC Network scenario: Traffic split through SGWs

This example mentions explicitly scenario #1, but in case of scenario #2 (i.e.
Backhaul L2) configuration is very similar, only difference is that MSTP has to
be enabled and that VLAN tagging towards L2 Backhaul is done in MLS. In
case of IPSEC with Backhaul L2 traffic is routed in MLS, not switched.
BSC CPU and PCU IP endpoints are organized in Subnet as following (see /A/
for overview):

DN0976623 © 2014 Nokia Networks 75 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

• O&M Subnet
• SIGTRAN-1 Subnet
• SIGTRAN-2 Subnet
• OMUSIG Subnet
• TRXSIG Subnet
• ETPSIG-c Subnet
• ETPSIG-m Subnet
• Gb Subnet
Error! Reference source not found.Figure 24 shows an example of MLSs
connected to one BSC, one TP5000, one A-2200 and a redundant pair of
SGWs. MLS is composed of two main functionalities as depicted in the picture
(Switching + Routing functions):

• MLSs see SWUs as next hop routers.

• ETP IP endpoints for AoIP or PWE Ater belong to BSC-SITE-BB Subnet
(a.b.2.0/xx).
• ETP IP endpoints for PAoEth U/S-plane or PWE Abis belong to BSC-
SITE-BH Subnet (a.b.3.0/xx).
• Traffic through L2 Ports is forwarded by internal switch to internal router.
• SVI-1, SVI-3, SVI-U0 and SVI-T0 are defined in MLS-0.
• SVI-2, SVI-4, SVI-U1 and SVI-T1 are defined in MLS-1.
• TP5000 and A-2200 Setup are described in /B/.
• Juniper SGW Setup is described in /C/.
• Policy Based routing has to be used to address traffic as in Error!
Reference source not found.Figure 23.

Note:
In this example /30 subnets are used in case of next hop
router, whereas /24 subnets are used otherwise.
However, /24 subnets have been chosen for readability
purposes but the correct subnet size actually depends on
the network configuration.

DN0976623 © 2014 Nokia Networks 76 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

MLS-0 BSC #1
SWU-0

Backbone-0 a.b.1.1/30 a.b.1.5/30 a.b.1.6/30

BB-00 BS1-00
Backhaul-0
BH-00 BS1-01
a.b.1.25/30 a.b.1.9/30 a.b.1.10/30

a.b.9.7
SWU-2

a.b.2.2
a.b.3.2
a.b.4.3
a.b.5.3
SGW-0 (Netscreen)

a.b.4.1 U-00

SVI-U0
SVI-T0

SVI-3
SVI-1
a.b.5.1 T-00

U-00
PTP-M (Tp5000) T-00 BS1-02 ETP-0
IMC a.b.2.6 SP-00 a.b.2.4
a.b.9.7
SP-01 BS1-04

SP-02 ETP-1
a.b.2.5
a.b.9.7
IOC 1
a.b.3.6
a.b.3.7

Virtual@
a.b.3.1

a.b.2.1

HSRP
IOC 2
ETP-2
a.b.3.4

SP-01
ETP-3
SP-02
AA-00 BS1-02 a.b.3.5
AA-01
BS1-04
a.b.2.7 AA-02
ATS (A-2200)
a.b.3.8
SVI-U1

a.b.3.9
SVI-T1
.3 SVI-4
SVI-2

a.b.5.2 T-00
a.b.9.7

T-00
a.b.2.3
a.b.4.4
a.b.5.4
a.b.3

U-00 U-00
a.b.4.2
SGW-1 (Netscreen) SWU-1
a.b.1.29/30 a.b.1.17/30 a.b.1.18/30
Backhaul-1 BS1-00
BH-00
Backbone-1 BB-00 BS1-01
a.b.1.13/30 a.b.1.21/30 a.b.1.22/30
MLS-1 SWU-3

Note 1: In this picture ETP means generally ETIP, ETPE, ETPA

Note 2: A-2200 redundancy aspects are not included in this picture (see /B/)

DN0976623 © 2014 Nokia Solutions and Networks 77 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Figure 24: Example of MLS configuration (Backbone L3 and Backhaul L3 + IPSEC)

5.3.3.2 L3 ports provisioning

L3 ports provisioning is summarized in Error! Reference source not
found.Table 23. (Link aggregation is not considered in the table).

Table 25: L3 port provisioning (network scenario #1 with IPSEC)

Next hop
MLS ID Port ID IP address Subnet Usage
unit
MLS-0 BB-00 Edge Router a.b.1.1 a.b.1.0/30 Backbone
interface
BS1-00 SWU-0 a.b.1.5 a.b.1.4/30 O&M, CBC,
SIGTRAN based
interfaces (A, Lb,
BBI, VNP),
PAoEth c/m,
external ETPSIG
BS1-01 SWU-2 a.b.1.9 a.b.1.8/30 GboIP interface
MLS-1 BB-00 Edge Router a.b.1.13 a.b.1.12/30 Backbone
interface
BS1-00 SWU-1 a.b.1.17 a.b.1.16/30 O&M, CBC,
SIGTRAN based
interfaces (A, Lb,
BBI, VNP),
PAoEth c/m,
external ETPSIG
BB-00 SWU-3 a.b.1.21 a.b.1.20/30 GboIP interface

MLS-0 BH-00 Edge Router a.b.1.25 a.b.1.24/30 Backhaul

interface
MLS-1 BH-00 Edge Router a.b.1.29 a.b.1.28/30 Backhaul
interface

5.3.3.3 VLAN & Subnet provisioning

In this example ETP and Synch Devices endpoints are organized in
SubNet/VLAN as summarized in Error! Reference source not found.Table
24. .

DN0976623 © 2014 Nokia Networks 78 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Table 26: VLANs/Subnet provisioning (FlexiBSC; network scenario #1 with IPSEC)

VLAN/Subnet
VLAN ID Subnet Usage
Nickname
BSC-SITE-BB 20 a.b.2.0/24 AoIP IP Endpoints
PWE Ater IP Endpoints
Synch Device Management IP
Endpoints
BSC-SITE-BH 30 a.b.3.0/24 PAoEth U IP Endpoints
PWE Abis IP Endpoints
Synch Device S-plane IP Endpoints
BSC-SITE-U Untagged a.b.4.0/24 Untrusted traffic IP Endpoints
BSC-SITE-T Untagged a.b.5.0/24 Trusted traffic IP Endpoints

Table 27: SVI (network scenario #1 with IPSEC)

MLS ID SVI ID VLAN ID IP address IP Subnet

MLS-0 SVI-1 21 a.b.2.2 a.b.2.0/24
MLS-0 SVI-3 31 a.b.3.2 a.b.3.0/24
MLS-0 SVI-U0 Untagged a.b.4.3 a.b.4.0/24
MLS-0 SVI-T0 Untagged a.b.5.3 a.b.5.0/24

MLS-1 SVI-2 21 a.b.2.3 a.b.2.0/24

MLS-1 SVI-4 31 a.b.3.3 a.b.3.0/24
MLS-1 SVI-U1 Untagged a.b.4.4 a.b.4.0/24
MLS-1 SVI-T1 Untagged a.b.5.4 a.b.5.0/24

5.3.3.4 L2 port provisioning

Table 28: L2 port provisioning (FlexiBSC; network scenario #1 with IPSEC)

MLS ID Port ID Next hop unit Spanning tree Usage

MLS-0 BS1-02 ETP Host AoIP (TC in MGW) or PWE Ater

DN0976623 © 2014 Nokia Networks 79 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

MLS ID Port ID Next hop unit Spanning tree Usage

BS1-04 ETP Host Packet Abis or PWE Abis

U-00 SGW-0 Host Untrusted traffic

T-00 SGW-0 Host Trusted traffic

SP-00 PTP-M Host PTP-M Management

SP-01 PTP-M Host S-plane (PTP messages)
SP-02 PTP-M Host S-plane (PTP messages)

IM-00 & MLS-1 Trunk Inter MLS connection

IM-01 (Link
Agg)
MLS-1 BS1-02 ETP Host AoIP (TC in MGW) or PWE Ater
BS1-04 ETP Host Packet Abis or PWE Abis

U-00 SGW-0 Host Untrusted traffic

T-00 SGW-0 Host Trusted traffic

SP-01 PTP-M Host S-plane (PTP messages)

SP-02 PTP-M Host S-plane (PTP messages)

AA-00 ATS Host Management

AA-01 ATS Host S-plane (Dummy PWE)
AA-02 ATS Host S-plane (Dummy PWE)

IM-00 & MLS-0 Trunk Inter MLS connection

IM-01 (Link
Agg)

DN0976623 © 2014 Nokia Networks 80 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

5.3.3.5 PBR (Policy based routing)

Concept of Policy Based Routing (PBR) is explained below:
• Policy-based routing is applied to incoming packets.
• All packets received on an interface with enabled policy-based
routing are considered for policy-based routing.
• Packets pass through enhanced packet filters are called route
maps.
• Based on the match criteria defined in the route maps, packets are
forwarded/routed according to specified action.
• If packet does not match with any match clause in the route map
normal forwarding applies.

Steps to enable PBR on an interface are the following:

1. Define a route map.
2. Specify the match criteria. In case of IPSEC GSM RAN the
following match criteria is recommended:
• Match the source and destination IP address that is
permitted by one or more standard or extended access
lists (ACL).
If you do not specify a match command, the route map applies to
all packets.

3. Specify the action or actions to take on the packets that match

the criteria. In principle there are different kinds of actions. In
case of IPSEC GSM RAN, the following action is
recommended:
• Set next hop to which to route the packet (the next hop
must be adjacent).
4. Identify the route map to use for PBR. One interface can only
have one route-map tag, but you can have multiple route map
entries with different sequence numbers. These entries are
evaluated in sequence number order until the first match. If
there is no match, packets will be routed as usual.
For commands please look at CISCO documentation for
example, following links:

DN0976623 © 2014 Nokia Networks 81 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Access List:
http://www.cisco.com/en/US/products/sw/secursw/ps1018/prod
ucts_tech_note09186a00800a5b9a.shtml
PBR:
http://www.cisco.com/en/US/products/sw/secursw/ps1018/prod
ucts_tech_note09186a00800a5b9a.shtml

Table 29: PBR configuration in MLS-0 (FlexiBSC; network scenario #1 with IPSEC)

Interf Route Map Match clause Action

(Standard or extended ACL)
Tag Seq Source action
Nu Subnet Dst Subnet
m
BS1-00 BSC-SW 10 permit O&M any route to SGW trust interf (a.b.5.1)
20 permit SIGTRAN-1 any route to SGW trust interf (a.b.5.1)
30 permit OMUSIG any route to SGW trust interf (a.b.5.2)
40 permit TRXSIG any route to SGW trust interf (a.b.5.2)
50 permit Ext ETPSIG any route to SGW trust interf (a.b.5.2)
BS1-01 BSC-SW 10 permit Gb any route to SGW trust interf (a.b.5.2)
BS1-02 ETP 10 permit ETP-BB any route to SGW trust interf (a.b.5.1)
BS1-04 ETP 10 permit ETP-BH any route to SGW trust interf (a.b.5.2)
SP-00 PTP-IMC 10 permit ETP-BB any route to SGW trust interf (a.b.5.1)
SP-01 PTP-IOC1 10 permit ETP-BH any route to SGW trust interf (a.b.5.2)
SP-02 PTP-IOC2 10 permit ETP-BH any route to SGW trust interf (a.b.5.2)
BB-00 Backbone- 10 permit any O&M route to SGW untrust interf (a.b.4.1)
0
20 permit any SIGTRAN route to SGW untrust interf (a.b.4.1)
1
30 permit any Ext route to SGW untrust interf (a.b.4.2)
ETPSIG
40 permit any Gb route to SGW untrust interf (a.b.4.2)
50 permit any ETP-BB route to SGW untrust interf (a.b.4.1)
BH-00 Backhaul-0 10 permit any OMUSIG route to SGW untrust interf (a.b.4.2)
20 permit any TRXSIG route to SGW untrust interf (a.b.4.2)
30 permit any ETP-BH route to SGW untrust interf (a.b.4.2)

DN0976623 © 2014 Nokia Networks 82 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Interf Route Map Match clause Action

(Standard or extended ACL)
Tag Seq Source action
Nu Subnet Dst Subnet
m
IM-0 1 permit O&M any route to SGW trust interf (a.b.5.1)
2 permit SIGTRAN-1 any route to SGW trust interf (a.b.5.1)
3 permit OMUSIG any route to SGW trust interf (a.b.5.2)
4 permit TRXSIG any route to SGW trust interf (a.b.5.2)
5 permit Ext ETPSIG any route to SGW trust interf (a.b.5.2)
6 permit Gb any route to SGW trust interf (a.b.5.2)
7 permit ETP-BB any route to SGW trust interf (a.b.5.1)
8 permit ETP-BH any route to SGW trust interf (a.b.5.2)
9 permit ETP-BB any route to SGW trust interf (a.b.5.1)
10 permit ETP-BH any route to SGW trust interf (a.b.5.2)
11 permit ETP-BH any route to SGW trust interf (a.b.5.2)
12 permit any O&M route to SGW untrust interf (a.b.4.1)
13 permit any Ext route to SGW untrust interf (a.b.4.2)
ETPSIG
14 permit any Gb route to SGW untrust interf (a.b.4.2)
15 permit any ETP-BB route to SGW untrust interf (a.b.4.1)
16 permit any OMUSIG route to SGW untrust interf (a.b.4.2)
17 permit any TRXSIG route to SGW untrust interf (a.b.4.2)
18 permit any ETP-BH route to SGW untrust interf (a.b.4.2)

U-00 … Normal forwarding at traffic in this interface

T-00 … Normal forwarding at traffic in this interface

MLS-1 has similar configuration (the differences between MLS-0 and MLS-1
are marked in blue).

DN0976623 © 2014 Nokia Networks 83 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Table 30: PBR configuration in MLS-1 (FlexiBSC; network scenario #1 with IPSEC)

Interf Route Map Match clause Action

(Standard or extended
ACL)
action
Tag Seq Source
Dst Subnet
Num Subnet
BS1-00 BSC-SW 10 permit O&M any route to SGW trust interf
(a.b.5.1)
20 permit SIGTRAN-2 any route to SGW trust interf
(a.b.5.2)
30 permit OMUSIG any route to SGW trust interf
(a.b.5.2)
40 permit TRXSIG any route to SGW trust interf
(a.b.5.2)
50 permit Ext ETPSIG any route to SGW trust interf
(a.b.5.2)
BS1-01 BSC-SW 10 permit Gb any route to SGW trust interf
(a.b.5.2)
BS1-02 ETP 10 permit ETP-BB any route to SGW trust interf
(a.b.5.1)
BS1-04 ETP 10 permit ETP-BH any route to SGW trust interf
(a.b.5.2)

SP-01 PTP- 10 permit ETP-BH any route to SGW trust interf

IOC1 (a.b.5.2)
SP-02 PTP- 10 permit ETP-BH any route to SGW trust interf
IOC2 (a.b.5.2)
BB-00 Backbone 10 permit any O&M route to SGW untrust interf
-0 (a.b.4.1)
20 permit any SIGTRAN-2 route to SGW untrust interf
(a.b.4.2)
30 permit any Ext ETPSIG route to SGW untrust interf
(a.b.4.2)
40 permit any Gb route to SGW untrust interf
(a.b.4.2)
50 permit any ETP-BB route to SGW untrust interf
(a.b.4.1)

DN0976623 © 2014 Nokia Networks 84 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Interf Route Map Match clause Action

(Standard or extended
ACL)
action
Tag Seq Source
Dst Subnet
Num Subnet
BH-00 Backhaul- 10 permit any OMUSIG route to SGW untrust interf
0 (a.b.4.2)
20 permit any TRXSIG route to SGW untrust interf
(a.b.4.2)
30 permit any ETP-BH route to SGW untrust interf
(a.b.4.2)

IM-0 1 permit O&M any route to SGW trust interf

(a.b.5.1)
2 permit SIGTRAN-2 any route to SGW trust interf
(a.b.5.2)
3 permit OMUSIG any route to SGW trust interf
(a.b.5.2)
4 permit TRXSIG any route to SGW trust interf
(a.b.5.2)
5 permit Ext ETPSIG any route to SGW trust interf
(a.b.5.2)
6 permit Gb any route to SGW trust interf
(a.b.5.2)
7 permit ETP-BB any route to SGW trust interf
(a.b.5.1)
8 permit ETP-BH any route to SGW trust interf
(a.b.5.2)
9 permit ETP-BB any route to SGW trust interf
(a.b.5.1)
10 permit ETP-BH any route to SGW trust interf
(a.b.5.2)
11 permit ETP-BH any route to SGW trust interf
(a.b.5.2)
12 permit any O&M route to SGW untrust interf
(a.b.4.1)
13 permit any Ext ETPSIG route to SGW untrust interf
(a.b.4.2)
14 permit any Gb route to SGW untrust interf
(a.b.4.2)

DN0976623 © 2014 Nokia Networks 85 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Interf Route Map Match clause Action

(Standard or extended
ACL)
action
Tag Seq Source
Dst Subnet
Num Subnet
15 permit any ETP-BB route to SGW untrust interf
(a.b.4.1)
16 permit any OMUSIG route to SGW untrust interf
(a.b.4.2)
17 permit any TRXSIG route to SGW untrust interf
(a.b.4.2)
18 permit any ETP-BH route to SGW untrust interf
(a.b.4.2)
AA-00 ATS-Man 10 permit ETP-BB any route to SGW trust interf
(a.b.5.1)
AA-01 ATS-S 10 permit ETP-BH any route to SGW trust interf
(a.b.5.2)
AA-02 ATS-S 10 permit ETP-BH any route to SGW trust interf
(a.b.5.2)

U-00 … Normal forwarding at traffic in this interface

T-00 … Normal forwarding at traffic in this interface

5.3.3.6 HSRP provisioning

The overview is available in section 5.2.5.

Table 31: HSRP configuration (FlexiBSC; reference scenario #1 with IPSEC)

HSRP
MLS Group
VLAN IP address Group ID Virtual router IP
prio

21 MLS-0 a.b.2.2 110 21 a.b.2.1

MLS-1 a.b.2.3 90
31 MLS-0 a.b.3.2 90 31 a.b.3.1
MLS-1 a.b.3.3 110

DN0976623 © 2014 Nokia Networks 86 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

5.3.3.7 OSPF
The overview is available in section 5.2.6.

Note:
OSPF has to be enabled on SVI-T, SVI-U also.

5.4 Provisioning examples: mcBSC

5.4.1 Reference scenario #1 (Backbone/Backhaul L3) with no mcTC

5.4.1.1 Overview
The so called Reference scenario #1 (Backbone L3 + Backhaul L3) is described in BSC
Transport Site Solution Mother Document /A/.

Figure 25 shows an example of such a scenario where MLSs are connected to

one mcBSC when AoIP (with TC in MGW) is concerned. One TP5000 and one
A-2200 are also connected to MLSs. MLS is composed by two main
functionalities as depicted in the picture (Switching + Routing functions):
• Traffic through L2 Ports is forwarded by internal switch to
internal router.
• SVI-1, SVI-3, SVI-5, SVI-7, SVI-9, SVI-11, SVI-13, SVI-15
and SVI-17 are defined in MLS-0.
• SVI-2, SVI-4, SVI-6, SVI-8, SVI-10, SVI-12, SVI-14, SVI-16
and SVI-18 are defined in MLS-1.
• TP5000 and A-2200 Setup is described in /B/.
Within the BSC site, mcBSC units and Synch devices IP endpoints are
organized in Subnets as follows (see /A/ for overview):
• O&M Subnet
• SIGTRAN-1 Subnet
• SIGTRAN-2 Subnet
• AoIP Subnet
• GboIP Subnet

DN0976623 © 2014 Nokia Networks 87 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

• Packet Abis U-plane Subnet

• Packet Abis C-plane Subnet (TRXSIG)
• Packet Abis M-plane Subnet (OMUSIG)
• Synchronization Subnet

Note:
In this example /30 subnets are used in case of next hop router,
whereas /24 subnets are used otherwise. However, /24 subnets have
been chosen for readability purposes but the correct subnet size actually
depends on the network configuration.

5.4.1.2 L3 port provisioning

L3 port provisioning is summarized in Table 32.

Table 32: L3 port provisioning (mcBSC; reference scenario #1; no mcTC)

MLS ID Port ID Next hop unit IP address Subnet Usage

MLS-0 BB-00 Edge Router a.b.1.1 a.b.1.0/30 Backbone
interface
MLS-1 BB-00 Edge Router a.b.1.13 a.b.1.12/30 Backbone
interface
MLS-0 BH-00 Edge Router a.b.1.25 a.b.1.24/30 Backhaul
interface
MLS-1 BH-00 Edge Router a.b.1.29 a.b.1.28/30 Backhaul
interface

5.4.1.3 VLAN & Subnet provisioning

In this example mcBSC units and Synch devices are organized in Subnets and VLANs as
summarized in Table 33.

Table 33: VLAN/Subnet provisioning (mcBSC; reference scenario #1; no mcTC)

VLAN/Subnet Nickname VLAN ID Subnet Endpoints in the Subnet

BSC-SITE-o&m 20 a.b.2.0/24 mcBSC O&M IP endpoints
(OMU)

DN0976623 © 2014 Nokia Networks 88 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

BSC-SITE-sigtran-1 30 a.b.3.0/24 mcBSC SIGTRAN-1 IP

endpoints (MCMU,
BCXU)
BSC-SITE-sigtran-2 40 a.b.4.0/24 mcBSC SIGTRAN-2 IP
endpoints (MCMU,
BCXU)
BSC-SITE-aoip 50 a.b.5.0/24 mcBSC AoIP IP endpoints
(ETMA)
BSC-SITE-gboip 60 a.b.6.0/24 mcBSC GboIP IP
endpoints (PCUM)
BSC-SITE-pabis-u 70 a.b.7.0/24 mcBSC Packet Abis U-
plane IP endpoints
(ETME)
BSC-SITE-pabis-c 80 a.b.8.0/24 mcBSC Packet Abis C-
plane IP endpoints
(BCXU)
BSC-SITE-pabis-m 90 a.b.9.0/24 mcBSC Packet Abis M-
plane IP endpoints
(BCXU)
BSC-SITE-sync 100 a.b.10.0/24 Synch Device S-plane IP
endpoints, mcBSC
integrated Synch Master
IP endpoints (PTU)

Table 34: SVI (mcBSC; reference scenario #1; no mcTC)

MLS ID SVI ID VLAN ID IP address Subnet Usage

SVI-1 20 a.b.2.2 a.b.2.0/24 O&M
SVI-3 30 a.b.3.2 a.b.3.0/24 SIGTRAN-1
SVI-5 40 a.b.4.2 a.b.4.0/24 SIGTRAN-2
SVI-7 50 a.b.5.2 a.b.5.0/24 AoIP
SVI-9 60 a.b.6.2 a.b.6.0/24 GboIP
MLS-0
Packet Abis U-
SVI-11 70 a.b.7.2 a.b.7.0/24
plane
Packet Abis C-
SVI-13 80 a.b.8.2 a.b.8.0/24
plane
Packet Abis M-
SVI-15 90 a.b.9.2 a.b.9.0/24
plane
SVI-17 100 a.b.10.2 a.b.10.0/24 Synchronization

DN0976623 © 2014 Nokia Networks 89 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

SVI-2 20 a.b.2.3 a.b.2.0/24 O&M

SVI-4 30 a.b.3.3 a.b.3.0/24 SIGTRAN-1
SVI-6 40 a.b.4.3 a.b.4.0/24 SIGTRAN-2
SVI-8 50 a.b.5.3 a.b.5.0/24 AoIP
SVI-10 60 a.b.6.3 a.b.6.0/24 GboIP
MLS-1
Packet Abis U-
SVI-12 70 a.b.7.3 a.b.7.0/24
plane
Packet Abis C-
SVI-14 80 a.b.8.3 a.b.8.0/24
plane
Packet Abis M-
SVI-16 90 a.b.9.3 a.b.9.0/24
plane
SVI-18 100 a.b.10.3 a.b.10.0/24 Synchronization

5.4.1.4 L2 port provisioning

Table 35: L2 port provisioning (mcBSC; reference scenario #1; no mcTC)

MLS ID Port ID Next hop unit Spanning Tree Usage

O&M, GboIP,
BS1-00 Module-2 switch Host
SIGTRAN
BS1-01 & BS-02 (Link
Module-2 switch Host AoIP
Agg)
BS1-03 & BS-04 (Link
Module-2 switch Host Packet Abis
Agg)
mcBSC integrated
MLS-0 BS1-05 Module-2 PTU Host
Sync master
SP-00 PTP-M Host PTP-M Management
S-plane (PTP
SP-01 PTP-M Host
messages)
S-plane (PTP
SP-02 PTP-M Host
messages)
IM-00 & IM-01 (Link
MLS-1 Trunk Inter MLS connection
Agg)
O&M, GboIP,
BS1-00 Module-1 switch Host
SIGTRAN
BS1-01 & BS-02 (Link
Module-1 switch Host AoIP
Agg)
MLS-1
BS1-03 & BS-04 (Link
Module-1 switch Host Packet Abis
Agg)
mcBSC integrated
BS1-05 Module-1 PTU Host
Sync master

DN0976623 © 2014 Nokia Networks 90 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

S-plane (PTP
SP-01 PTP-M Host
messages)
S-plane (PTP
SP-02 PTP-M Host
messages)
AA-00 ATS Host ATS Management
S-plane (Empty
AA-01 ATS Host
Dummy PW)
S-plane (Empty
AA-02 ATS Host
Dummy PW)
IM-00 & IM-01 (Link
MLS-0 Trunk Inter MLS connection
Agg)

5.4.1.5 HSRP provisioning

Overview in section 5.2.5. In this example:

• MLS-0 is the master for O&M, SIGTRAN-1 and AoIP traffic.

• MLS-1 is the master for SIGTRAN-2, GboIP and Packet
Abis traffic (optional integrated Sync Master as well).

Table 36: HSRP configuration (mcBSC; reference scenario #1; no mcTC)

HSRP
VLAN MLS IP address Virtual router
Group prio Group ID
IP
MLS-0 a.b.2.2 110
20 20 a.b.2.1
MLS-1 a.b.2.3 90
MLS-0 a.b.3.2 110
30 30 a.b.3.1
MLS-1 a.b.3.3 90
MLS-0 a.b.4.2 90
40 40 a.b.4.1
MLS-1 a.b.4.3 110
MLS-0 a.b.5.2 110
50 50 a.b.5.1
MLS-1 a.b.5.3 90
MLS-0 a.b.6.2 90
60 60 a.b.6.1
MLS-1 a.b.6.3 110
MLS-0 a.b.7.2 90
70 70 a.b.7.1
MLS-1 a.b.7.3 110

DN0976623 © 2014 Nokia Networks 91 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

MLS-0 a.b.8.2 90
80 80 a.b.8.1
MLS-1 a.b.8.3 110
MLS-0 a.b.9.2 90
90 90 a.b.9.1
MLS-1 a.b.9.3 110
MLS-0 a.b.10.2 90
100 100 a.b.10.1
MLS-1 a.b.10.3 110

5.4.2 Reference scenario #1 (Backbone/Backhaul L3) with remote mcTC

5.4.2.1 Overview
The so called Reference scenario #1 (Backbone L3 + Backhaul L3) is described in
BSC Transport Site Solution Mother Document /A/.

Figure 26 shows an example of such a scenario where MLSs are connected to one
mcBSC when AoIP (with TC in BSS) is concerned and mcTC is located in a remote
site wrt to mcBSC. One TP5000 and one A-2200 are also connected to MLSs. MLS
is composed by two main functionalities as depicted in the picture (Switching +
Routing functions):

• Traffic through L2 Ports is forwarded by internal switch to

internal router.
• SVI-1, SVI-3, SVI-5, SVI-7, SVI-9, SVI-11, SVI-13, SVI-15,
SVI-17 and SVI-19 are defined in MLS-0.
• SVI-2, SVI-4, SVI-6, SVI-8, SVI-10, SVI-12, SVI-14, SVI-
16, SVI-18 and SVI-20 are defined in MLS-1.
• TP5000 and A-2200 Setup is described in /B/.

Within the BSC site, mcBSC units and Synch devices IP endpoints are organized in
Subnets as follows (see /A/ for overview):

• O&M Subnet
• SIGTRAN-1 Subnet
• SIGTRAN-2 Subnet
• GboIP Subnet
• Packet Abis U-plane Subnet

DN0976623 © 2014 Nokia Networks 92 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

• Packet Abis C-plane Subnet (TRXSIG)

• Packet Abis M-plane Subnet (OMUSIG)
• Packet Ater Subnet 8
• Synchronization Subnet
• ETPSIG Subnet 8

Note:
in this example /30 subnets are used in case of next hop router, whereas
/24 subnets are used otherwise. However, /24 subnets have been
chosen for readability purposes but the correct subnet size actually
depends on the network configuration.

8
In this example Packet Ater UL and Packet Ater DL share the same subnet but it might happen that two
separated subnets are configured. Same holds for ETPSIG-c and ETPSIG-m.

5.4.2.2 L3 port provisioning

L3 port provisioning is summarized in Table 37.

Table 37: L3 port provisioning (mcBSC; reference scenario #1; remote mcTC)

MLS ID Port ID Next hop unit IP address Subnet Usage

MLS-0 BB-00 Edge Router a.b.1.1 a.b.1.0/30 Backbone
interface
MLS-1 BB-00 Edge Router a.b.1.13 a.b.1.12/30 Backbone
interface
MLS-0 BH-00 Edge Router a.b.1.25 a.b.1.24/30 Backhaul interface
MLS-1 BH-00 Edge Router a.b.1.29 a.b.1.28/30 Backhaul interface

5.4.2.3 VLAN & Subnet provisioning

In this example mcBSC units and Synch devices are organized in Subnets and
VLANs as summarized in Table 38.

Table 38: VLAN/Subnet provisioning (mcBSC; reference scenario #1; remote mcTC)

VLAN/Subnet
VLAN ID Subnet Endpoints in the Subnet
Nickname
BSC-SITE-o&m 20 a.b.2.0/24 mcBSC O&M IP endpoints (OMU)

DN0976623 © 2014 Nokia Networks 93 / 100

Issue 01C
 BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

BSC-SITE-sigtran-1 30 a.b.3.0/24 mcBSC SIGTRAN-1 IP endpoints (MCMU, BCXU)

BSC-SITE-sigtran-2 40 a.b.4.0/24 mcBSC SIGTRAN-2 IP endpoints (MCMU, BCXU)
mcBSC Packet Ater DL and Packet Ater UL endpoints
BSC-SITE-pater 50 a.b.5.0/24
(ETMA and ETME respectively)
BSC-SITE-gboip 60 a.b.6.0/24 mcBSC GboIP IP endpoints (PCUM)
BSC-SITE-pabis-u 70 a.b.7.0/24 mcBSC Packet Abis U-plane IP endpoints (ETME)
BSC-SITE-pabis-c 80 a.b.8.0/24 mcBSC Packet Abis C-plane IP endpoints (BCXU)
BSC-SITE-pabis-m 90 a.b.9.0/24 mcBSC Packet Abis M-plane IP endpoints (BCXU)
Synch Device S-plane IP endpoints, mcBSC integrated
BSC-SITE-sync 100 a.b.10.0/24
Synch Master IP endpoints (PTU)
BSC-SITE-etpsig 110 a.b.11.0/24 mcBSC ETPSIG-c and ETPSIG-m endpoints (BCXU)

Table 39: SVI (mcBSC; reference scenario #1; remote mcTC)

MLS ID SVI ID VLAN ID IP address Subnet Usage

SVI-1 20 a.b.2.2 a.b.2.0/24 O&M
SVI-3 30 a.b.3.2 a.b.3.0/24 SIGTRAN-1
SVI-5 40 a.b.4.2 a.b.4.0/24 SIGTRAN-2
SVI-7 50 a.b.5.2 a.b.5.0/24 Packet Ater
SVI-9 60 a.b.6.2 a.b.6.0/24 GboIP
MLS-0
SVI-11 70 a.b.7.2 a.b.7.0/24 Packet Abis U-plane
SVI-13 80 a.b.8.2 a.b.8.0/24 Packet Abis C-plane
SVI-15 90 a.b.9.2 a.b.9.0/24 Packet Abis M-plane
SVI-17 100 a.b.10.2 a.b.10.0/24 Synchronization
SVI-19 110 a.b.11.2 a.b.11.0/24 ETPSIG
SVI-2 20 a.b.2.3 a.b.2.0/24 O&M
SVI-4 30 a.b.3.3 a.b.3.0/24 SIGTRAN-1
SVI-6 40 a.b.4.3 a.b.4.0/24 SIGTRAN-2
SVI-8 50 a.b.5.3 a.b.5.0/24 Packet Ater
SVI-10 60 a.b.6.3 a.b.6.0/24 GboIP
MLS-1
SVI-12 70 a.b.7.3 a.b.7.0/24 Packet Abis U-plane
SVI-14 80 a.b.8.3 a.b.8.0/24 Packet Abis C-plane
SVI-16 90 a.b.9.3 a.b.9.0/24 Packet Abis M-plane
SVI-18 100 a.b.10.3 a.b.10.0/24 Synchronization
SVI-20 110 a.b.11.3 a.b.11.0/24 ETPSIG

DN0976623 © 2014 Nokia Networks 94 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

5.4.2.4 L2 port provisioning

Table 40: L2 port provisioning (mcBSC; reference scenario #1; remote mcTC)

MLS ID Port ID Next hop unit Spanning Tree Usage

BS1-00 Module-2 switch Host O&M, GboIP, SIGTRAN, ETPSIG
BS1-01 & BS-02 (Link Agg) Module-2 switch Host Packet Ater
BS1-03 & BS-04 (Link Agg) Module-2 switch Host Packet Abis
BS1-05 Module-2 PTU Host mcBSC integrated Sync master
MLS-0
SP-00 PTP-M Host PTP-M Management
SP-01 PTP-M Host S-plane (PTP messages)
SP-02 PTP-M Host S-plane (PTP messages)
IM-00 & IM-01 (Link Agg) MLS-1 Trunk Inter MLS connection
BS1-00 Module-1 switch Host O&M, GboIP, SIGTRAN, ETPSIG
BS1-01 & BS-02 (Link Agg) Module-1 switch Host Packet Ater
BS1-03 & BS-04 (Link Agg) Module-1 switch Host Packet Abis
BS1-05 Module-1 PTU Host mcBSC integrated Sync master
SP-01 PTP-M Host S-plane (PTP messages)
MLS-1
SP-02 PTP-M Host S-plane (PTP messages)
AA-00 ATS Host ATS Management
AA-01 ATS Host S-plane (Empty Dummy PW)
AA-02 ATS Host S-plane (Empty Dummy PW)
IM-00 & IM-01 (Link Agg) MLS-0 Trunk Inter MLS connection

5.4.2.5 HSRP provisioning

Overview in section 5.2.5. In this example:

• MLS-0 is the master for O&M, SIGTRAN-1 and Packet Ater

traffic.
• MLS-1 is the master for SIGTRAN-2, GboIP, ETPSIG and
Packet Abis traffic (optional integrated Sync Master as
well).

DN0976623 © 2014 Nokia Networks 95 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Table 41: HSRP configuration (mcBSC; reference scenario #1; remote mcTC)

HSRP
VLAN MLS IP address
Group prio Group ID Virtual router IP
MLS-0 a.b.2.2 110
20 20 a.b.2.1
MLS-1 a.b.2.3 90
MLS-0 a.b.3.2 110
30 30 a.b.3.1
MLS-1 a.b.3.3 90
MLS-0 a.b.4.2 90
40 40 a.b.4.1
MLS-1 a.b.4.3 110
MLS-0 a.b.5.2 110
50 50 a.b.5.1
MLS-1 a.b.5.3 90
MLS-0 a.b.6.2 90
60 60 a.b.6.1
MLS-1 a.b.6.3 110
MLS-0 a.b.7.2 90
70 70 a.b.7.1
MLS-1 a.b.7.3 110
MLS-0 a.b.8.2 90
80 80 a.b.8.1
MLS-1 a.b.8.3 110
MLS-0 a.b.9.2 90
90 90 a.b.9.1
MLS-1 a.b.9.3 110
MLS-0 a.b.10.2 90
100 100 a.b.10.1
MLS-1 a.b.10.3 110
MLS-0 a.b.11.2 90 110
110 a.b.11.1
MLS-1 a.b.11.3

5.4.3 Others

Below a few hints on scenarios that can be seen as variants or combination of the
ones already described in previous sections of this document.

5.4.3.1 Reference scenario #2 (Backbone L3 + Backhaul L2)

As far as the Reference scenario #2 (Backbone L3 + Backhaul L2) is concerned
(see also BSC Transport Site Solution Mother Document /A/), provisioning is similar
to the Reference scenario #1 (see 5.4.1 and 5.4.2 above) with the following main
differences:

• From the Backhaul perspective, BTSs are organized in N

groups (N=2 in this example, i.e. two groups) by using

DN0976623 © 2014 Nokia Networks 96 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION BSC transport site solution: MLS Setup

Subnets/VLANs (additional option is to have separate

VLAN for M-plane and the rest of the Packet Abis traffic).
• Such Subnets/VLANs have to be configured into MLSs in
addition to those used for mcBSC units.
• Additional SVIs have to be configured in MLSs so that
appropriate routing is possible between backhaul VLANs
and mcBSC VLANs and vice versa.

5.4.3.2 Scenarios with IPSEC

Provisioning in case of IPSEC is essentially following the same principles
described in sub. 5.3.3 for FlexiBSC.
In mcBSC case traffic split is summarized in Figure 26 where, in comparison
with the FlexiBSC case, Packet Ater is included and PWE Ater/Abis excluded.

Figure 255: IPSEC Network scenario: Traffic split through SGWs (mcBSC)

DN0976623 © 2014 Nokia Networks 97 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION Appendices

6 Appendices

6.1 Juniper Products

6.1.1 Overview on JUNIPER Products (Routers and Switches)

6.1.2 Portfolio overview

Below a first rough overview on Juniper products that might suit the needs of the BSC
Transport Site solution.
For the time being Juniper is considered as a possible alternative approach to CISCO and a
more comprehensive analysis is left for future versions of the document (or to be moved to a
separate document). This might change especially in case of specific requests from
operators.
As part of Juniper EX-series (stackable solution for Ethernet switches), EX4200 is
considered as suitable at least for some configurations and some use cases in RG20(BSS)
on top. At the moment cannot be used when SyncE is chosen as synchronization solution.
The EX product family also includes EX4500 and EX8200 models, which are more targeted
for 10GE environment.
A few models from Juniper MX-series are currently used together with A-series in Nokia
Mobile Backhaul but not recommended since not yet tested as a site solution switch/router.
Juniper M- and T-series routers are currently used as intermediate routers in mobile operator
backbone applications and not recommended as well (not tested by Nokia so far).

DN0976623 © 2014 Nokia Networks 98 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION Appendices

6.1.3 Product comparison

A comparison of the some Juniper products is summarized in the following table including
technical limitations and an indication of what could be the recommended/alternative choice
from Nokia perspective.

Table 42: Juniper products - comparison and Nokia advice

Technical
Model Nokia Advice Remarks
Limitations

No WAN Not suitable in all use cases. Used/tested

Interfaces. SyncE in the Nokia Labs in Packet Core, MSS and
Suitable with
EX4200 not supported. RNC environments. It does not provide
limitation
ETH-LM not WAN interfaces (LAN only) and it cannot
supported be used if SyncE is required.

No WAN Not suitable in all use cases and not

Suitable with Interfaces. SyncE tested by Nokia. It does not provide WAN
EX8200 limitation / Not not supported. interfaces and cannot be used if SyncE is
Recommended ETH-LM not required. Not Recommended because not
supported tested by Nokia.

Not suitable in all use cases and not

No WAN tested by Nokia. Similar to 7600 as far as
MX960 Suitable with Interfaces. SyncE routing is concerned, but mainly used for
MX480 limitation / Not not supported. campus application. Not recommended
MX240 Recommended ETH-LM not because not tested by Nokia. Listed here
supported because currently used as CET core
device.

Not suitable in all use cases and not

ETH-LM not
M-series Not Suitable supported
tested by Nokia. Listed here because
currently used as backbone router.

Not suitable in all use cases and not

ETH-LM not
T-series Not Suitable supported
tested by Nokia. Listed here because
currently used as backbone router.

Note:
ETH-LB is supported by Juniper EX, MX, M and T series. For Juniper M,
MX and T series, please see the link below (ETH - OAM)

hhttp://www.juniper.net/techpubs/en_US/junos10.1/information-products/topic-
collections/config-guide-network-interfaces/configuring-ITU-T-Y-1731.html

DN0976623 © 2014 Nokia Networks 99 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION Appendices

References
TB TIS Telco Billing Blueprint Interfaces
P50020-Q1182-C200-xx-76D6

Integration Layer SW Design Description, Charge@Once business

Integration Layer Architecture Specification

DN0976623 © 2014 Nokia Networks 100 / 100

Issue 01C
BSC TRANSPORT SITE SOLUTION Appendices

DN0976623 © 2014 Nokia Networks 101 / 101

Issue 01C