RMEN - 3G IP Mobile Backhaul Architecture and Guidelines Ver0.0

RMEN 3G IP Mobile Backhaul Architecture & Guidelines
Reliance Mobile - 3G Services - A futuristic mobile experience
RMEN- 3G IP Mobile Backhaul

Architecture & Guidelines
Version 0.0
DRAFT
Reliance Communications Ltd (DAKC)

Thane Belapur Road
Navi Mumbai
PIN- 400709
0 0 15-11-2010 NSMK/ HS/ PK NSMK/ HS/ PK Mr Ja la j Choud hri
Version Revision Date Made By Checked By Approved By
RMEN 3G Architecture Reliance Confidential
Page 1 of 69 Release V0.0
A printed copy of this document is considered uncontrolled

Copyright 2007 Reliance Communication Limited. All rights reserved.

All brand or product names are trademarks of their respective companies or organizations.
NOTICE OF DISCLAIMER
RELIANCE INFOCOMM MAKES NO REPRESENTATION OR WARRANTY, EXPRESSED OR IMPLIED, WITH RESPECT TO

THE SUFFICIENCY, ACCURACY, OR UTILITY OF ANY INFORMATION OR OPINION CONTAINED IN THIS DOCUMENT
INCLUDING ANY WARRANTIES OF TITLE, NONINFRINGEMENT OF COPYRIGHT OR PATENT RIGHTS OF OTHERS.
THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN AS-IS BASIS.
RELIANCE INFOCOMM ADVISES THAT ANY USE OF OR RELYING UPON THE INFORMATION OR OPINION
CONTAINED IN THIS DOCUMENT IS AT THE SOLE RISK OF THE USER AND THAT RELIANCE INFOCOMM SHALL
NOT BE IN ANY MATTER BE LIABLE FOR ANY DAMAGE OR INJURY DIRECTLY OR INDIRECTLY INCURRED BY ANY
PERSON ARISING OUT OF THE SUFFICIENCY, ACCURACY, OR UTILITY OF ANY INFORMATION OR OPINION
CONTAINED HEREIN.
LOCAL CONDITIONS MAY GIVE RISE TO A NEED FOR ADDITIONAL PROFESSIONAL INVESTIGATIONS,
MODIFICATIONS, OR SAFEGUARDS TO MEET SITE, EQUIPMENT, AND ENVIRONMENTAL SAFETY OR COMPANY-
SPECIFIC REQUIREMENTS. IN NO EVENT IS THIS INFORMATION INTENDED TO REPLACE CENTRAL, STATE,
LOCAL, OR OTHER APPLICABLE CODES, LAWS, OR REGULATIONS. SPECIFIC APPLICATIONS OR USE OF THE
INFORMATION HEREIN WILL CONTAIN VARIABLES UNKNOWN TO OR BEYOND THE CONTROL OF RELIANCE
INFOCOMM. AS A RESULT, RELIANCE INFOCOMM CANNOT WARRANT THAT THE APPLICATION OR USE OF THIS
INFORMATION WILL PRODUCE THE TECHNICAL RESULT OR SAFETY ORIGINALLY INTENDED.
THIS IS NOT TO BE CONSTRUED AS A SUGGESTION TO ANYONE TO MODIFY OR CHANGE ANY PRODUCT OR
SERVICE, NOR DOES THIS DOCUMENT REPRESENT ANY COMMITMENT BY ANYONE, INCLUDING BUT NOT
LIMITED TO RELIANCE INFOCOMM TO PURCHASE, MANUFACTURE, OR SELL ANY PRODUCT WITH THE
DESCRIBED CHARACTERISTICS. READERS ARE SPECIFICALLY ADVISED THAT ANY ENTITY MAY HAVE NEEDS,
SPECIFICATIONS, OR REQUIREMENTS DIFFERENT FROM THE GENERIC DESCRIPTIONS HEREIN. THEREFORE,
ANYONE WISHING TO KNOW ANY ENTITYS NEEDS, SPECIFICATIONS, OR REQUIREMENTS SHOULD
COMMUNICATE DIRECTLY WITH THAT ENTITY. NOTHING CONTAINED HEREIN SHALL BE CONSTRUED AS
CONFERRING BY IMPLICATION, ESTOPPEL, OR OTHERWISE ANY LICENSE OR RIGHT UNDER ANY PATENT,
WHETHER OR NOT THE USE OF ANY INFORMATION HEREIN NECESSARILY EMPLOYS AN INVENTION OF ANY
EXISTING OR LATER ISSUED PATENT.
RELIANCE INFOCOMM DOES NOT HEREBY RECOMMEND, APPROVE, CERTIFY, WARRANT, GUARANTEE, OR
ENDORSE ANY PRODUCTS, PROCESSES, OR SERVICES, AND NOTHING CONTAINED HEREIN IS INTENDED OR
SHOULD BE UNDERSTOOD AS ANY SUCH RECOMMENDATION, APPROVAL, CERTIFICATION, WARRANTY,
GUARANTY, OR ENDORSEMENT TO ANYONE.
THE DOCUMENT TO WHICH THIS NOTICE IS ATTACHED IS PROTECTED BY COPYRIGHT OWNED IN WHOLE OR IN
PRINCIPAL PART BY RELIANCE INFOCOMM LIMITED. YOU MAY USE THE DOCUMENT ONLY FOR THE LIMITED
PURPOSES SPECIFIED BY RELIANCE INFOCOMM.
ANY DISTRIBUTION OF COPIES OF THE DOCUMENT OR ANY ALTERED VERSION THEREOF IS EXPRESSLY
PROHIBITED WITHOUT PRIOR WRITTEN CONSENT OF RELIANCE INFOCOMM
RELIANCE INFOCOMM RESERVES THE RIGHT TO REVISE THIS DOCUMENT FOR ANY REASON.

1 Contents
1 Contents .................................................................................................................................................................. 3
2 About This Design Document .................................................................................................................................. 4
2.1 Document Purpose .................................................................................................................................................. 4
2.2 Document Audience................................................................................................................................................. 4
2.3 Document Usage Guidelines .................................................................................................................................... 4
2.4 Assumptions ............................................................................................................................................................ 4
3 Network Overview .................................................................................................................................................... 5
4 3G-IP Mobile Backhaul Architecture ........................................................................................................................ 6
4.1 Introduction............................................................................................................................................................. 6
4.2 Scope.. ..................................................................................................................................................... 7
4.2 Layer 3 MPLS VPN Deployment Model for 3G .......................................................................................................... 7
4.3 Network Topology - Huawei RNC & Node-B............................................................................................................. 8
4.3.1 Connectivity between Huawei M-2000 at RNC & MEN ............................................................................................. 9
4.4 Network Topology - ZTE RNC & Node-B .................................................................................................................. 9
4.4.1 Network Topology - ZTE RNC & Node-B (Management) ........................................................................................... 9
4.4.2 Network Topology - ZTE RNC & Node-B (Service) .................................................................................................. 10
4.5 VLAN Assignments for Node-B Management and Services ..................................................................................... 10
4.5 .1 Management VLAN for Node-B ............................................................................................................................... 10
4.5 .2 Service VLAN for Node-Bs ...................................................................................................................................... 10
4.6 VRF Attributes for Services and Management ........................................................................................................ 11
4.7 Connectivity between Node-B & MEN Network:...................................................................................................... 11
5.1.3 Configurations on Huawei CX600 at Spoke Location Serving for Huawei Node-B .................................................. 20
5.1.4 Configurations on Cisco 7609 at Spoke Location Serving for Huawei Node-B ........................................................ 21
5.2 Configurations of MEN Devices at ZTE RNC and Node B locations ........................................................................ 22
5.2.1 Configurations on Huawei CX600 Connecting to ZTE RNC .................................................................................... 22
5.2.2 Configurations on Cisco 7609 Connecting to ZTE RNC at Hub Location ................................................................ 23
5.2.3 Configurations on CX600 at Spoke Location Serving for ZTE Node-Bs ................................................................... 24
5.2.4 Configurations on Cisco 7609 at Spoke Location Serving for ZTE Node-Bs ............................................................ 25
5.3 Configurations on MEN Switch at take-off Site ...................................................................................................... 26
5.3.1 Configurations on CX200 Serving for Node-B, MW SDH/PDH and IP Radio .......................................................... 26
5.3.2 Configurations on ME3400 Serving for Node-B ...................................................................................................... 29
5.3.3 Configurations on C3550 Serving for Node-B ......................................................................................................... 31
6 CX200D Configuration for NFS location Connecting to take-Off site ...................................................................... 32
6.1 NFS location Connecting to take-Off site of ME3400 and CX200D ......................................................................... 32
6.2 NFS Location Connecting to take-Off site C3550 .................................................................................................. 47
7 Bandwidth Provisioning on NLD path and MW sites in Small City / IS locations ................................................... 59
7.1 Sample Topology Diagram of IS location in NLD path ............................................................................................ 59
7.2 Bandwidth Calculations......................................................................................................................................... 60
7.2.1 BW to be provisioned in NLD path in each stretch ................................................................................................. 60
7.2.2 BW to be provisioned in Microwave SDH ............................................................................................................... 60
7.2.3 BW to be provisioned in IP Radio & Microwave PDH:- ............................................................................................ 60
8 Port mappings between IP Radio and BN/NFS BN nodes ....................................................................................... 60
8.1 IP Radio Port Mapping ........................................................................................................................................... 60
8.2 CX200 Port Mapping.............................................................................................................................................. 61
9 Process and Clarity Work flow ............................................................................................................................... 61
9.1 ImplimentationTask List MW ............................................................................................................................... 61
9.2 Service Attributes- MW MNGT ............................................................................................................................... 62
9.3 RIC_3G_Services Work Flow ................................................................................................................................... 62
9.4 RIC_3G _Service ATTRIBUTES ............................................................................................................................. 63
9.5 CP_Access_DATA_NFS Work Flow ........................................................................................................................... 64
9.6 CP_ACCESS_DATA_NFS ATTRIBUTES ................................................................................................................. 65
10.0 3G architecture for IBS locations ............................................................................................................................ 66
10.1 IBS Deployment Scenarios ....................................................................................................................................... 66
11.0 Architecture of 3G services for 3G Non RNC locations: ............................................................................................ 68

2 About This Design Document
Authors: Karunanithi NSM, Hemanshu Shah, Pramod P Kulkarni, Team NPEMEN

Reliance Communications Ltd.
Approver: Sh Jalaj Choudhri
2.1 Document Purpose
The purpose of this document is to explain the Process, 3G Backhaul Architecture and Rollout
Plan of the RCOM 3G Project. It details the physical and logical requirements and how the
network will accomplish the requirements to deliver the 3G services.
2.2 Document Audience
Reliance Technical Team, Management and Authorized Vendors if any.
2.3 Document Usage Guidelines
This document consists of a number of components. These include
Network Backhaul Topology and Design

Backhaul Configurations with respect to 3G IUB traffic
IP Plan details
Backhaul Provisioning Process
Guidelines for Bandwidth Provisioning on NLD path and Microwave sites in IS locations for
3G Service
The document should be used as a guideline for deriving the necessary information to ultimately
create the configurations that allow the network to provide the 3G services. This should be used
in conjunction with the deployment/field units to understand the topology, backhaul requirements
and the configurations. This will also allow the deployment engineer to take certain decisions
when deploying and configuring the network.
As long as the document is in a draft format, it may be modified by team NPE MEN. Any
suggestions may be provided to team NPE-MEN.
2.4 Assumptions

NPE MEN defines/tunes the missing architecture items according to best practices and
experiences gained.
It is assumed that the reader is familiar with Reliance Metro Ethernet Network and related
Architectures. Furthermore, it is also assumed the reader has basic understanding of the IP/MPLS
network and related technologies that will be used to fulfill the 3G IP Mobile Backhaul
requirements.
3 Network Overview
Reliance Metro Ethernet Network Solution can be divided into four business solution areas, these
are
Ethernet to Business
Ethernet to Home
IP Mobile Backhaul
Carriers Carrier
The Reliance Metro Ethernet network is designed to cater to triple play services (Data, Voice and
Video) for Residential, Corporate and Carriers Customers. Each solution has different
architectural and commercial scopes, but are similar in core design and infrastructure.
Network Stability and Scalability OSPF is used as the IGP routing protocol that scales well,
if the routing information is stable. Stability of backbone IGP was one of the main considerations
for the RMEN network.
Network Resiliency - RMEN MPLS network is intended to have a high degree of availability in
the core. Physical and logical design ensures that primary and backup path exists for any given
node.
Network Security - Implemented best-practices security mechanisms across the network

elements interfacing to Customers and on NNIs.
Simplicity - RMEN MPLS network design is clean and simple to understand and maintain.
Quality-of-Service - Traffic prioritization, Classes of Platinum, Gold, Silver, Best Effort of

Services are implemented in the network. Each class has different QoS attributes and guaranteed
(configured) minimum bandwidth available during congestion periods.

4 3G-IP Mobile Backhaul Architecture
4.1 Introduction
3G or 3rd Generation, is a generation of standards for mobile phones and mobile

telecommunications services fulfilling specifications by the International Telecommunication
Union.[1] Application services include wide-area wireless voice telephone, mobile Internet
access, video calls and mobile TV, all in a mobile environment
The 3G-RAN contains the base stations, which are called Node Bs, and Radio Network
Controllers (RNC)
The RNC provides control functionalities for one or more Node Bs. typical implementations have
a separate RNC located in a central office serving multiple Node Bs, logical interface between
them known as the Iub. The RNC and its corresponding Node Bs are called the Radio Network
Subsystem (RNS).
There are four interfaces connecting the 3G-RAN internally or externally to other functional
entities: Iu, Uu, Iub and Iur
The Iu interface is an external interface that connects the RNC to the Core Network (CN).
The Uu is also external, connecting the Node B with the User Equipment (UE).
The Iub is an internal interface connecting the RNC with the Node B

The Iur is an internal interface connecting two RNCs with each other.
Reliance MEN network is acting as a IP mobile backhaul Transport connectivity between IuB
interface at RNC & NodeBs
4.2 Scope
Phase 1 is aimed to make IP backhaul ready for the number of BTS at the following 3G Circles
being operational,
Assam - 399
Bihar - 629
Delhi - 2886
Himachal Pradesh - 87
Jammu & Kashmir - 440
Kolkata - 1650
Madhya Pradesh - 698
Mumbai - 2660
North East - 478
Orissa - 478
Punjab - 872
Rajasthan - 795
West Bengal - 321
4.2 Layer 3 MPLS VPN Deployment Model for 3G
This option makes optimal use of the IP NodeB acting as an IP host supporting static/default
routing. The solution distributes the IP/MPLS capabilities out to the edge of the network. This
will allow full dynamic switching/routing capabilities out into the pre-aggregation and
aggregation layers.
This design gives the redundancy capabilities of IP/MPLS with convergence techniques from end
to end. This solution also offers the possibility of supporting MPLS VPNs where multiple
different traffic types dictate a need for virtualization or isolation. The solution is also an efficient
backhaul option with little transport overhead, because there is no emulation. The redundancy
options available at the pre-aggregation edge includes of MSTP, offering path redundancy for
nodes.
Also, fast convergence triggering mechanism such as VRRP with BFD is proposed to be
implemented at RNC to MEN connecting interfaces.
Backhaul architecture on Metro is specifically designed to incorporate different vendors

equipment compatibility and specifications. Currently there are two different topologies proposed
with respect Huawei and ZTE RNC and Node-B requirements.

- Network Topology describing Huawei RNC and NodeB

- Network Topology describing ZTE RNC and NodeB
4.3 Network Topology - Huawei RNC & Node-B

4.3.1 Connectivity between Huawei M-2000 at RNC & MEN
4.4 Network Topology - ZTE RNC & Node-B
4.4.1 Network Topology - ZTE RNC & Node-B (Management)

4.4.2 Network Topology - ZTE RNC & Node-B (Service)
4.5 VLAN Assignments for Node-B Management and Services
4.5 .1 Management VLAN for Node-B
Node-Bs under one BAN will be placed on a separate management VLAN (VLAN56)
Management VLAN of Node-B to be passed start from the connecting interfaces of BN nodes
till Parenting BAN in the corresponding ring.
Management Vlan for both Huawei and ZTE Node-Bs VLAN 56
4.5 .2 Service VLAN for Node-Bs
Each Node-B under one BAN is assigned with separate VLAN for services and attached with
the common service VRF created in the BAN. Service VLAN of Node-B to be passed start from
the connecting interfaces of BN nodes till Parenting BAN in the corresponding ring.
Range of Service Vlan for both Huawei and ZTE Node-Bs VLAN 1600 1900

4.6 VRF Attributes for Services and Management
VRF Name
Detailed Below with respect to services and Management
Route Distinguisher (RD)
<Loopback1:RT>
Route Target (RT)
Detailed below with respect to services and Management
4.7 Connectivity between Node-B & MEN Network:
- Connectivity between MEN BN Switch & Node-B

- Connectivity between PDH Microwave Radio& Node-B
- Connectivity between SDH Microwave Radio & Node-B
- Connectivity between IP-Radio & Node-B

4.7.1 Node-B Connectivity Scenarios
Scenario 1
Scenario describes the Node-B connectivity directly to take off site, i.e. Fiber BTS site.
At fiber BTS site MEN NE will be available and it will be part of MEN Ring. To keep the
identical architecture for 3G , Port Number FE/FA-08 to FE/FA-14 are proposed ( in case the
proposed ports are in use, circle FA deploy team to assign new ports) for connecting the Node-B
to MEN switch. These ports will be configured as a trunk port.By default Node-B management
VLAN 56 will be allowed and service VLAN to be configured against the Node-B service SO,
the detailed configuration is covered in subsequent section.
Scenario 2

Above mentioned Scenario-2 gives the idea about connectivity between Node-B and take-off site
NE when Node-Bis connected behind 1st Hop SDH ad another Node-B connected behind 2nd
Hop PDH card.
For making connectivity from 1st Hop Node-B to Take-off site NE, it has been proposed to
install the CX-200 at 1st Hop BTS location below SDH MW connecting to L1 card or IMAP card
of SDH NE. To make this CX-200 RFS and to carry the Node-B service and Management traffic
, bearer needs to be created between this CX-200 to take off site. The process for making this
CX-200 RFS and bearer creation is mentioned in details in subsequent section.
For making connectivity from 2nd Hop Node-B to Take-off site NE, it has been proposed to
commission 2-Port Ethernet card in PDH device. Node-B will connect to ethernet card. Also the
PDH will connect to CX-200D installed at 1st HOP BTS location to carry this traffic to RNC as
shown in above diagram.
In this Scenario the rule mentioned for take off Site will remain same as mentioned in scenario-
1, as multiple Node-Bs to be provisiond under single interface of take-off site, then number of
service VLAN needs to be provisioned against the Node-B Service SO. For Configuring the CX-
200 at 1st HOP BTS location, switch configuration and ports are decided and mentioned in
details in below section.
However FA_DEPOY_CIRCLE team has to provide the correct interface details of take-offsite
NE for each Node B provisioning.
Scenario 3

In above mentioned Scnario-3 two PDH HOPs are terminating on CX-200 installed at 1st Hop
BTS location. The configuration of CX-200 and port mapping is as per details mentioned in
above scenarios. FA_DEPLOY_Circle team to give the correct Interface details of take-off site
and respective Node-B service SO.
Scenario 4
In scenario number 4, the IP Radio link terminating on Fiber BTS MEN NE. As mentioned in
above scenario, the rules remain same for connecting to take of site. Node B will connect
directly to IP Radio for 1st HOP and 2nd Hop Node-B will connect to PDH Ethernet card.
The visibility of these Microwave devices will be as per Microwave DCN architecture document.
The bearer to be provisioned in each Hop based on availiblity of bandwidth. In case of IP Radio
the bandwidth required other than 2G BTS to be converted to IP radio, (for bandwidth calculation
refer the guidelines released by MW Planning Team)

Scenario 5
In Scenario Number 5 the IP Radio link will terminate on Fiber BTS MEN NE and Tail-End NEs
are PDH MW. In this scenario we have deployed CX-200D below IP radio for serving more than
one PDH link. IP Radio has 4 number of ethernet ports , In case of Ethernet port requirement is
more than four then we are proposing to commission CX-200D below IP radio. From same IP
radio we can serve up to four number of Ethernet connectivity. IP radio port mapping is covered
in subsequent setion below.

Scenario 6
For Scnario number 6 , The rules defined in above mentioned scenarios will remain same for
connecting to Take off site NE, To provision CX200D at BTS location, For bearer provisioning.
For bearer creation we are proposing 60Mbps bandwidth on each hop, In case 60Mbps is not
available, provisioining can be made based on available bandwidth, provided at leaset 2Mbps*no.
of NodeBs downstream is available.

Scenario 7
For Scenario number 7, the rules defined in above mentioned scenarios will remain same for
connecting to take off site NE, to provision CX200D at BTS location, for bearer provisioning,
refer port mapping as explained below.
For bearer creation, 60Mbps bandwidth proposed on each Microwave SDH hop, In case 60Mbps
is not available, provisioining can be made based on available bandwidth, provided at leaset
2Mbps*no. of NodeBs downstream is available.
FA_DEPLOY_CICLE has to map correct port of take off site for provisioning the Node-Bs
service vlans.

Scenario 8
This Scenario number is for provisioning the 3G services on NLD BTS route. In this scenario
CX-200 is proposed in each BTS location.
For bearer bandwidth requirement refer section 7.1
For providing the protection to this TX route, Manual Bearer SO to be raised by circle team from
last point to aggregation location for total amount of bandwidth.
Scenario 9

This Scenario is same like the scenario number 8. CX-200D is proposed below each SDH NE.
For bearer bandwidth requirement refer section 7.1
For providing the protection to this TX route, Manual Bearer SO to be raised by circle team from
last point to aggregation location for total amount of bandwidth.
5 Configuration Guidelines
5.1 Configurations of MEN Devices at Huawei RNC and Node B locations
5.1.1 Configurations on Huawei CX600 Connecting to Huawei RNC at Hub Location
#
ip vpn-instance Hub-Huawei-3G-MNGT
route-distinguisher <loopback IP:RT>
vpn-target <hub RT> export-extcommunity
vpn-target <spoke management RT> <spoke service RT> import-extcommunity
#
interface Gig x/y/z
description *** Hub-Huawei-3G-MNGT *****
ip binding vpn-instance Hub-Huawei-3G-MNGT
ip address <IP Address > <mask >
#
bgp 65000
#
ipv4-family vpn-instance Hub-Huawei-3G-MNGT
import-route static
import-route direct
#
ip route-static vpn-instance Hub-Huawei-3G-MNGT <ip address> <mask> <RNC IP Address>
#
5.1.2 Configurations on Cisco 7609 Connecting to Huawei RNC at Hub Location

!
ip vrf Hub-Huawei-3G-MNGT
rd <loopback IP:RT>
route-target export <hub RT>
route-target import <spoke management RT>
route-target import <spoke service RT>
!
vlan <XXXX>
name Hub-Huawei-3G-MNGT
!
interface vlan <XXXX>
ip vrf forwarding Hub-Huawei-3G-MNGT
no ip redirects
no ip directed-broadcast

no cdp enable
exit-address-family
!
ip route vrf Hub-Huawei-3G-MNGT <ip address> <mask> <RNC IP Address> [permanent]
!
router bgp 65000
!
address-family ipv4 vrf Hub-Huawei-3G-MNGT
redistribute static
redistribute connected
no auto-summary
no synchronization
exit-address-family
!
5.1.3 Configurations on Huawei CX600 at Spoke Location Serving for Huawei Node-B
#
ip vpn-instance Spoke-Huawei-3G-MNGT
route-distinguisher <loopback IP: Spoke_Mngmt_RT>
vpn-target < RT-MNGT> export-extcommunity
vpn-target <Hub_RT> import-extcommunity
#
ip vpn-instance Spoke-Huawei-3G-SERVICE
route-distinguisher <loopback IP: Spoke_Service_RT >
vpn-target < RT-SERVICE > export-extcommunity
vpn-target <Hub_RT> import-extcommunity
#
vlan <XXXX>
description *** Spoke-Huawei-3G-MNGT ***
#
vlan <YYYY>
description *** Spoke-Huawei-3G-SERVICE ***
#
description *** Spoke-Huawei-3G-MNGT *****
ip binding vpn-instance Spoke-Huawei-3G-MNGT
#
interface vlan <YYYY>
description *** Spoke-Huawei-3G-SERVICE *****
ip binding vpn-instance Spoke-Huawei-3G-SERVICE
#
bgp 65000
#
ipv4-family vpn-instance Spoke-Huawei-3G-MNGT
import-route direct
#
ipv4-family vpn-instance Spoke-Huawei-3G-SERVICE
import-route direct
#

5.1.4 Configurations on Cisco 7609 at Spoke Location Serving for Huawei Node-B
!
ip vrf Spoke-Huawei-3G-MNGT
rd <loopback IP:Spoke_MNGT_RT>
route-target export < Spoke_MNGT_RT >
route-target import <Hub_Management RT>
!
ip vrf Spoke-Huawei-3G-SERVICE
rd <loopback IP:Spoke_Service_RT>
route-target export < Spoke_Service_RT >
route-target import <Hub_Service_RT>
!
vlan <XXXX>
!
vlan <YYYY>
!
ip vrf forwarding Spoke-Huawei-3G-MNGT
no ip redirects
no cdp enable
exit-address-family
!
ip vrf forwarding Spoke-Huawei-3G-SERVICE
no ip redirects
no cdp enable
exit-address-family
!
router bgp 65000
!
address-family ipv4 vrf Spoke-Huawei-3G-MNGT
no auto-summary
no synchronization
exit-address-family
!
address-family ipv4 vrf Spoke-Huawei-3G-SERVICE
no auto-summary
no synchronization
exit-address-family
!

5.2 Configurations of MEN Devices at ZTE RNC and Node B locations
5.2.1 Configurations on Huawei CX600 Connecting to ZTE RNC
#
ip vpn-instance Hub-ZTE-3G-MNGT
route-distinguisher <loopback IP:Management RT>
vpn-target <Hub Management RT > export-extcommunity
vpn-target <Spoke Management RT> import-extcommunity
#
ip vpn-instance Hub-ZTE-3G-SERVICE
route-distinguisher <loopback IP:Hub Service RT>
vpn-target < Hub Service RT > export-extcommunity
vpn-target <Spoke Service RT> import-extcommunity
#
#
interface GigabitEthernet2/1/X ============ L2 Interface Connecting to RNC
description ****Connectivity to RNC*****
negotiation auto
undo shutdown
portswitch
set flow-stat interval 10
trust upstream default vlan Management VLAN, Service VLAN>
trust 8021p vlan Management VLAN, Service VLAN>
trust upstream default
port-queue be wfq weight 30port-wred nni-trunk-wred outbound
port-queue af2 wfq weight 33 port-wred nni-trunk-wred outbound
port-queue af4 wfq weight 40 port-wred nni-trunk-wred outbound
port-queue ef pq shaping shaping-percentage 10 outbound
undo lldp enable
#
interface GigabitEthernet2/1/X.< Management VLAN>
vlan-type dot1q <VLAN ID>
description *** Hub-ZTE-3G-MNGT *****
ip binding vpn-instance Hub-ZTE-3G-MNGT
ip address <Management IP address> <Mask>
#
interface GigabitEthernet2/1/X.< Service VLAN>
vlan-type dot1q <VLAN ID>
description *** Hub-ZTE-3G-SERVICE *****
ip binding vpn-instance Hub-ZTE-3G-SERVICE
ip address <Service IP address> <Mask>
#
bgp 65000
ipv4-family vpn-instance Hub-ZTE-3G-MNGT
import-route static

import-route direct
#
#
ipv4-family vpn-instance Hub-ZTE-3G-SERVICE
import-route static
import-route direct
#
ip route-static vpn-instance Hub-ZTE-3G-MNGT <ip address> <mask> <RNC Management IP Address>
#
ip route-static vpn-instance Hub-ZTE-3G-SERVICE <ip address> <mask> <RNC Service IP Address>
#
5.2.2 Configurations on Cisco 7609 Connecting to ZTE RNC at Hub Location
!
ip vrf Hub-ZTE-3G-MNGT
rd <loopback IP:Hub Management RT>
route-target export <Hub Management RT>
route-target import <Spoke management RT>
!
ip vrf Hub-ZTE-3G-SERVICE
rd <loopback IP:Hub Service RT>
route-target export <Hub Service RT>
route-target import <Spoke Service RT>
!
vlan <XXXX>
name Hub_ZTE_3G_MNGT
!
vlan <YYYY>
name Hub_ZTE_3G_SERVICE
!
interface GigabitEthernetX/Y
description ******Connectivity to RNCX*****
no ip address
load-interval 30
wrr-queue bandwidth 14 53 33
wrr-queue queue-limit 14 53 33
wrr-queue random-detect min-threshold 1 70 100 100 100 100 100 100 100
wrr-queue random-detect max-threshold 1 100 100 100 100 100 100 100 100
wrr-queue cos-map 1 1 1
hold-queue 2048 in
hold-queue 2048 out

!
interface GigabitEthernet1/7.XXXX <Management Vlan>
description ***** Hub-ZTE-3G-MNGT******
encapsulation dot1Q XXXX
ip vrf forwarding Hub-ZTE-3G-MNGT
ip address <Management IP Address > <mask >
no ip redirects
no cdp enable
exit-address-family
!
interface GigabitEthernet1/7.YYYY <Service Vlan>
description ***** Hub-ZTE-3G-SERVICE******
encapsulation dot1Q YYYY
ip vrf forwarding Hub-ZTE-3G-SERVICE
ip address <Service IP Address > <mask >
no ip redirects
no cdp enable
exit-address-family
!
ip route vrf Hub-ZTE-3G-MNGT <ip address> <mask> <RNC IP Address> [permanent]
ip route vrf Hub-ZTE-3G-SERVICE <ip address> <mask> <RNC IP Address> [permanent]
!
router bgp 65000
!
address-family ipv4 vrf Hub-ZTE-3G-MNGT
redistribute static
no auto-summary
no synchronization
exit-address-family
!
address-family ipv4 vrf Hub-ZTE-3G-SERVICE
redistribute static
no auto-summary
no synchronization
exit-address-family
!
5.2.3 Configurations on CX600 at Spoke Location Serving for ZTE Node-Bs
#
ip vpn-instance Spoke-ZTE-3G-MNGT

route-distinguisher <loopback IP: Spoke_Mngmt_RT>

vpn-target < Spoke Management RT> export-extcommunity
vpn-target <Hub Management_RT> import-extcommunity
#
ip vpn-instance Spoke-ZTE-3G-SERVICE
route-distinguisher <loopback IP: Spoke_Service_RT >
vpn-target < Spoke Service RT> export-extcommunity
vpn-target <Hub Service RT> import-extcommunity
#
vlan <XXXX>
description *** Spoke-ZTE-3G-MNGT ***
#
vlan <YYYY>
description *** Spoke-ZTE-3G-SERVICE ***
#
description *** Spoke-ZTE-3G-MNGT *****
ip binding vpn-instance Spoke-ZTE-3G-MNGT
#
description *** Spoke-ZTE-3G-SERVICE *****
ip binding vpn-instance Spoke-ZTE-3G-SERVICE
#
bgp 65000
#
ipv4-family vpn-instance Spoke-ZTE-3G-MNGT
import-route direct
#
ipv4-family vpn-instance Spoke-ZTE-3G-SERVICE
import-route direct
#
5.2.4 Configurations on Cisco 7609 at Spoke Location Serving for ZTE Node-Bs
!
ip vrf Spoke-ZTE-3G-MNGT
rd <loopback IP:Spoke_MNGT_RT>
route-target export < Spoke Management RT >
route-target import <Hub Management RT>
!
ip vrf Spoke-ZTE-3G-SERVICE
rd <loopback IP:Spoke_Service_RT>
route-target export < Spoke_Service_RT >
route-target import <Hub_Service_RT>
!
vlan <XXXX>
name Hub-ZTE-3G-MNGT
!
vlan <YYYY>
name Hub-ZTE-3G-MNGT
!


ip vrf forwarding Spoke-ZTE-3G-MNGT
no ip redirects
no cdp enable
exit-address-family
!
ip vrf forwarding Spoke-ZTE-3G-SERVICE
no ip redirects
no cdp enable
exit-address-family
!
router bgp 65000
!
address-family ipv4 vrf Spoke-ZTE-3G-MNGT
no auto-summary
no synchronization
exit-address-family
!
address-family ipv4 vrf Spoke-ZTE-3G-SERVICE
no auto-summary
no synchronization
exit-address-family
!
5.3 Configurations on MEN Switch at take-off Site
5.3.1 Configurations on CX200 Serving for Node-B, MW SDH/PDH and IP Radio
#
traffic classifier GWmac
if-match source-mac <BAN-Management-IP-Gateway-MAC>
#
traffic behavior GWmac
deny
#
traffic policy Block_GWmac
classifier GWmac behavior GWmac
#
#
interface Ethernet0/0/X
description ****Interface Connecting to SDH TX ********
port link-type trunk
port trunk allow-pass vlan 1 56 126 to 130
broadcast-suppression 10
stp enable

stp point-to-point force-true

stp config-digest-snoop
stp compliance dot1s
stp no-agreement-check
trust 8021p
negotiation auto
traffic-policy Block_GWmac inbound
loopback-detect enable
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
qos drr queue-index 0 weight 30
qos queue ef cir 100000 pir 100000
efm enable
efm error-frame period 10
efm error-frame threshold 5000
efm error-frame notification enable
efm threshold-event trigger error-shutdown
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
description ****Interface Connecting to IPRADIO********
port trunk allow-pass vlan 56 126 to 130
dhcp snooping check arp enable
dhcp snooping check ip enable
dhcp snooping check dhcp-chaddr enable
dhcp snooping check dhcp-request enable
dhcp snooping check dhcp-rate enable
negotiation auto
mac-table limit 50
port-security enable
port-security protect-action restrict
port-security aging-time 1
jumboframe enable
bpdu disable
bpdu filter enable
undo lldp enable
undo ntdp enable

undo ndp enable

qos drr
stp loop-protection
#
description ****Interface Connecting to PDH ********
port trunk allow-pass vlan 56
negotiation auto
mac-table limit 50
jumboframe enable
bpdu disable
bpdu filter enable
undo lldp enable
undo ntdp enable
undo ndp enable
qos drr
stp loop-protection
#
description ****Connectivity to NODE-B-1*******
port trunk allow-pass vlan 56


negotiation auto
mac-table limit 50
jumboframe enable
bpdu disable
bpdu filter enable
undo lldp enable
undo ntdp enable
undo ndp enable
qos drr
stp loop-protection
5.3.2 Configurations on ME3400 Serving for Node-B
!
mac access-list extended Block_GWmac
deny host <Gateway MAC> any
permit any any
!
!
interface FastEthernet0/x
switchport mode trunk
switchport trunk allowed vlan 56
switchport port-security
switchport port-security maximum 50
switchport port-security aging time 50
switchport port-security violation restrict
switchport port-security aging type inactivity
storm-control broadcast level 1.00
storm-control action trap
mac access-group Block_GWmac in
ip dhcp snooping limit rate 10
spanning-tree portfast
spanning-tree guard root

spanning-tree bpdufilter enable

no shutdown
!
description **** Connectivity to PDH *******
no shutdown
!
description **** Connectivity to IP Radio *******
no shutdown
!
switchport trunk allowed vlan 56 127


no shutdown
!
description **** Connectivity to SDH *******
port-type nni
switchport trunk allowed vlan 56 126-130
ip arp inspection trust
load-interval 30
ip dhcp snooping trust
ethernet oam
lldp run
!
5.3.3 Configurations on C3550 Serving for Node-B
!
mac access-list extended Block_GWmac
deny host <Gateway MAC> any
permit any any
!
ip dhcp snooping
no shutdown
!
description **** Connectivity to PDH *******


ip dhcp snooping
no shutdown
!
switchport trunk allowed vlan 56 127
ip dhcp snooping
no shutdown
!
description **** Connectivity to SDH *******
switchport trunk allowed vlan 56,126-130
ip arp inspection trust
load-interval 30
ip dhcp snooping trust
!
6 CX200D Configuration for NFS location Connecting to take-Off site
6.1 NFS location Connecting to take-Off site of ME3400 and CX200D
clock timezone IST add 5:30

system-view
#
sysname <Reliance_CX200D>

#
super password level 15 simple ril123
#
info-center source MSTP channel 3 trap level informational
info-center source MSTP channel 4 log level notification
info-center source SOCKET channel log host log level errors
info-center source SOCKET channel 8 log state off
#
firewall enable
#
igmp-snooping enable
#
error-shutdown auto-recovery cause efm-threshold-event
error-shutdown auto-recovery interval 300
#
vlan batch 1 to 4094
#
bpdu-tunnel lacp group-mac 0100-0ccd-cdd0
bpdu-tunnel pvst group-mac 0100-0ccd-cdd0
bpdu-tunnel stp group-mac 0100-0ccd-cdd0
bpdu-tunnel pagp group-mac 0100-0ccd-cdd0
bpdu-tunnel cdp group-mac 0100-0ccd-cdd0
bpdu-tunnel udld group-mac 0100-0ccd-cdd0
bpdu-tunnel vtp group-mac 0100-0ccd-cdd0
bpdu-tunnel sstp group-mac 0100-0ccd-cdd0
#
dhcp snooping enable
#
firewall defend all enable
undo firewall defend ip-spoofing enable
#
loopback-detect interval 5
#
mac-address restrict
#
undo cluster enable
#
undo ndp enable
#
undo ntdp enable
undo ntdp hop
#
lldp enable
#
efm enable
#
vlan 56
description *** Node B Management ***
loop-detect eth-loop alarm-only

#
stp region-configuration
region-name reliance
revision-level 1
instance 1 vlan 1100 to 1149 1500 to 1549
instance 9 vlan 999
instance 10 vlan 101 to 102 127 to 130 3100 to 4000
instance 11 vlan 2 to 100 103 to 126 131 to 998 1000 to 1005 1024 to 1099
active region-configuration
#
stp enable
stp converge normal
#
#
deny
#
#
traffic classifier default
if-match any
#
qos sred queue-index 0 red 700 discard-probability 1 yellow 1000 discard-probability 4
#
interface Vlanif127
description***** CX200 NFS Management VLAN ******
mtu 1540
ip address <ip-address/24>
firewall defend enable
#
interface Ethernet0/0/1
description ****CX-200D NFS Uplink :- To EPL-100 of SDH TX towards Takeoff site********


trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
description ****CX-200D NFS Uplink :- To IPRADIO towards Takeoff site********
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr


efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
description ****CX-200D NFS Uplink :- To PDH-1 towards Tail End side********
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#

trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr


efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection

#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
description ****CX-200D NFS Uplink :- To EPL-100 card of SDH-TX-1 towards Tail End side********
trust 8021p
negotiation auto

jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
efm enable


efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
description ****CX-200D NFS Uplink :- To IPRADIO-I towards Tail End side********

trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
description ****CX-200D NFS Uplink :- To IPRADIO-2 towards Tail End side********
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr


efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
efm enable
efm up-hold-time 50
efm trigger if-net
stp loop-protection
#
port trunk allow-pass vlan 1 56


negotiation auto
mac-table limit 50
jumboframe enable
bpdu disable
bpdu filter enable
undo lldp enable
undo ntdp enable
undo ndp enable
stp loop-protection
#
negotiation auto
mac-table limit 50
jumboframe enable
bpdu disable
bpdu filter enable
undo lldp enable
undo ntdp enable
undo ndp enable
stp loop-protection
#


negotiation auto
mac-table limit 50
jumboframe enable
bpdu disable
bpdu filter enable
undo lldp enable
undo ntdp enable
undo ndp enable
stp loop-protection
#
negotiation auto
mac-table limit 50
jumboframe enable
bpdu disable
bpdu filter enable
undo lldp enable
undo ntdp enable
undo ndp enable
stp loop-protection
#
description ****Reserved********
Shutdown
#
shutdown
#
Shutdown

#
description ****Reserved for Enterprise services********
Shutdown
#
Shutdown
#
Shutdown
#
Shutdown
#
interface GigabitEthernet0/0/1
Shutdown
#
Shutdown
#
interface NULL0
#
aaa
local-user ril password simple ril123
local-user ril level 1
#
ip route-static default-preference 1
ip route-static 0.0.0.0 0.0.0.0 Vlanif127 <BAN-Management-Gateway-IPaddress>
#
ntp-service source-interface Vlanif127
ntp-service unicast-server < BAN--Gateway-loopback0-IP>
#
lldp management-address <management-vlan-ipaddress>
#
user-interface maximum-vty 15
#
user-interface con 0
authentication-mode password
user privilege level 1
set authentication password simple ril123
#
user-interface vty 0 15
idle-timeout 15

6.2 NFS Location Connecting to take-Off site C3550
clock timezone IST add 5:30

system-view
#
sysname <Reliance_CX200D>
#
super password level 15 simple ril123
#
info-center source MSTP channel 3 trap level informational
info-center source SOCKET channel log host log level errors
#
firewall enable
#
igmp-snooping enable
#
error-shutdown auto-recovery cause efm-threshold-event
error-shutdown auto-recovery interval 300
#
vlan batch 1 to 4094
#
bpdu-tunnel lacp group-mac 0100-0ccd-cdd0
bpdu-tunnel pvst group-mac 0100-0ccd-cdd0
bpdu-tunnel stp group-mac 0100-0ccd-cdd0
bpdu-tunnel pagp group-mac 0100-0ccd-cdd0
bpdu-tunnel cdp group-mac 0100-0ccd-cdd0
bpdu-tunnel udld group-mac 0100-0ccd-cdd0
bpdu-tunnel vtp group-mac 0100-0ccd-cdd0
bpdu-tunnel sstp group-mac 0100-0ccd-cdd0
#
#
firewall defend all enable
undo firewall defend ip-spoofing enable
#
loopback-detect interval 5
#
mac-address restrict
#
undo cluster enable
#
undo ndp enable
#
undo ntdp enable
undo ntdp hop

#
lldp enable
#
efm enable
#
vlan 56
description *** Node B Management ***
loop-detect eth-loop alarm-only
#
stp region-configuration
region-name reliance
revision-level 1
instance 9 vlan 999
instance 10 vlan 101 to 102 127 to 130 3100 to 4000
instance 11 vlan 2 to 100 103 to 126 131 to 998 1000 to 1005 1024 to 1099
active region-configuration
#
stp enable
stp converge normal
#
#
deny
#
#
traffic classifier default
if-match any
#
#
interface Vlanif127
description***** CX200 NFS Management VLAN ******
mtu 1540

ip address <ip-address/24>
firewall defend enable
#
description ****CX-200D NFS Uplink :- To EPL-100 of SDH TX towards Takeoff site********
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
undo ntdp enable
undo ndp enable
qos drr
stp loop-protection
#
description ****CX-200D NFS Uplink :- To IPRADIO towards Takeoff site********
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
undo ntdp enable
undo ndp enable
qos drr


stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
lldp enable
bpdu enable
undo ntdp enable
undo ndp enable
qos drr


stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
stp loop-protection
#
trust 8021p
negotiation auto


jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
stp loop-protection
#


trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr


stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
stp loop-protection
#
description ****CX-200D NFS Uplink :- To IPRADIO-I towards Tail End side********
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable

undo ndp enable

qos drr
stp loop-protection
#
trust 8021p
negotiation auto
jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
stp loop-protection
#
trust 8021p
negotiation auto


jumboframe enable
bpdu enable
lldp enable
undo ntdp enable
undo ndp enable
qos drr
stp loop-protection
#
negotiation auto
mac-table limit 50
jumboframe enable
bpdu disable
bpdu filter enable
undo lldp enable
undo ntdp enable
undo ndp enable
stp loop-protection
#


negotiation auto
mac-table limit 50
jumboframe enable
bpdu disable
bpdu filter enable
undo lldp enable
undo ntdp enable
undo ndp enable
stp loop-protection
#
negotiation auto
mac-table limit 50
jumboframe enable
bpdu disable
bpdu filter enable
undo lldp enable
undo ntdp enable
undo ndp enable
stp loop-protection
#
negotiation auto

mac-table limit 50
jumboframe enable
bpdu disable
bpdu filter enable
undo lldp enable
undo ntdp enable
undo ndp enable
stp loop-protection
#
Shutdown
#
shutdown
#
Shutdown
#
Shutdown
#
Shutdown
#
Shutdown
#
Shutdown
#
Shutdown
#
Shutdown
#
interface NULL0

#
aaa
local-user ril password simple ril123
local-user ril level 1
#
ip route-static default-preference 1
ip route-static 0.0.0.0 0.0.0.0 Vlanif127 <BAN-Management-Gateway-IPaddress>
#
ntp-service source-interface Vlanif127
ntp-service unicast-server < BAN--Gateway-loopback0-IP>
#
lldp management-address <management-vlan-ipaddress>
#
user-interface maximum-vty 15
#
user-interface con 0
#
user-interface vty 0 15
idle-timeout 15
#
7 Bandwidth Provisioning on NLD path and MW sites in Small City / IS locations
7.1 Sample Topology Diagram of IS location in NLD path
NLD 10Gig Ring

Mecheda IS Kolkata MCN
STM-4 Ring STM-4 Ring

Kulgachia Bauria
BW to be provisioned in NLD path = (Number of BTS at Bauria x 2) + (Number of BTS in Kulgachia x 2)
Number of BTS at Bauria =X

Number of BTS in Kulgachia = Y
CX200 CX200
Required BW in NLD = (X*2)+(Y*2)Mbps
Node B
IP Radio MW PDH Node B
MW PDH
60Mbps
MW SDH
Node B
CX200
Node B
IP Radio MW PDH Node B
MW PDH
MW PDH Node B
Node B Node B
MW PDH Node IP Radio IP Radio MW PDH Node
B B
60Mbps Node B 60Mbps 60Mbps

MW SDH MW SDH MW SDH MW PDH
CX200 CX200 CX200
Node B
MW PDH Node B IP Radio MW PDH
MW PDH Node B
Node B Node B
MW PDH IP Radio MW PDH
Node B
60Mbps 60Mbps
Node B 60Mbps 60Mbps
MW SDH MW SDH
MW SDH MW SDH
CX200 CX200 CX200 CX200
Node B
IP Radio MW PDH
IP Radio MW PDH

7.2 Bandwidth Calculations
7.2.1 BW to be provisioned in NLD path in each stretch
BW to be provisioned in NLD path = (Number of BTS at Bauria x 2) + (Number of BTS in

Kulgachia x 2)
Number of BTS at Bauria =X

Number of BTS in Kulgachia = Y
For example:-
Number of BTS at Bauria = X = 30
Number of BTS at Kulgachia = Y = 2
Required BW in NLD = (X*2)+(Y*2)Mbps

= (30*2)+(2*2)Mbps
= (60)+(4)Mbps
Required BW in NLD = 64 Mbps
7.2.2 BW to be provisioned in Microwave SDH
BW to be provisioned in Microwave SDH :- 60Mbps on each hop, In case 60Mbps is not

available, provisioining can be made based on available bandwidth, provided at leaset 2Mbps*no.
of NodeBs downstream is available.
7.2.3 BW to be provisioned in IP Radio & Microwave PDH:-
BW to be provisioned in IP Radio & MW PDH: - Maximum Available Bandwidth (As

per NPE-MW guideline)
8 Port mappings between IP Radio and BN/NFS BN nodes
8.1 IP Radio Port Mapping
All the ports on IP Radio should be available for carrying traffic. No port should be
reserved for CX-200 for ONM. For ONM, NMS port is available on the IDU.
Port mapping is as follows:
a) Port No. 1 Towards take-off site

b) Port No. 2 Towards Tail end

c) Port No. 3 Towards Tail end

d) Port No. 4 Node-B
8.2 CX200 Port Mapping
Below are the proposed port mappings for CX-200D at BTS location.
9 Process and Clarity Work flow
9.1 ImplimentationTask List MW
The service type RIC_IMT_MW_MEN is defined for making the MW NEs Visible on MEN.
Below is the Service flow for Microwave NE Visibility on MEN along with workorder
instruction for each WG.

9.2 Service Attributes- MW MNGT

To Define the Service Fow pl. find herewith the attribute lost for service type
RIC_IMT_MW_MEN
9.3 RIC_3G_Services Work Flow
The RIC_3G_Services work flow defined for provisioning 3G services and Node-B management
configuration across MEN. These SOs would be generated by WG 3G_Circle_Lead which is

defined for each cirle. For raising these SOs Node B Service vlan, Node-B Management vlan,
Node-B Service IP address , Subnet Mask, Node B Managemnet IP Address, Subnet Mask and
Gateway IP address are the mandatory attributes. These attribute details to be provided by
FA_Deploy circle team. Initially the Node-B integration volume is to high, So based on attributes
details provided by FA_Deploy circle team, Auto SOs would be raised by Clarity team.
Pl. find below the sample work flow with work order instruction for RIC_3G_Services.
9.4 RIC_3G _Service ATTRIBUTES
Pl. find below the list of service attributes for raising the RIC_3G_services SO.

9.5 CP_Access_DATA_NFS Work Flow
CP_ACCESS_DATA_NFS work flow is the network build process for integrating CX-200D at
BTS location ( Non fiber site location).
The CX_200D will be commissioned at BTS location by Vendor, the necessary configuration
will be provided by FA_Deploy team. The CX-200D will be integrated in network with
predefined configuration. Also port mapping will as mentioned above.
For making CX-200D visible at BTS location, bearer need to be provisioned. If backhaul of
CX-200D is SDH then bearer needs to provisiond aginst the child SO.
RIC_IMT_MEN_DEBEARER.
If backhaul of of CX-200D is IP Radio then IP radio to be provisioned CX-200D visibility.

SOMG_TX team will be configuring the IP radio based on Mangement IP provided by
NPE_MW team.
Below is the proposed work flow for Visibility of CX-200D at NFS location.
TASKNAME SEQUENCE WORKGROUP Description

Circle Team to ensure that NDD/GIS/Clarity is completed
UNIT INSTALLATION 10 FA_DEPLOY_A
before closure of this step.
VALIDATE_SO 20 OSS_DEV Validating SO.
UPDATE_TASKS 30 OSS_DEV Tasks to load in clarity
UPDATE_SID 40 OSS_DEV Automated Task to update Subscriber_id for the Open SO.
AUTO PARAMETER Automated Task that Loads the Equipment parameters in
50 OSS_DEV
the Tool Pallete.
FIELD_AT 60 O&M_ADN_A 1.Node AT/Site Acceptance 2.Complete the Field AT.
ALLOCATE_IP_RADIO 70 NPE_MW To Insure the visibility of IP radio.
CREATE_CHILD_SO 80 OSS_DEV Raise RIL_IMT_MEN_DBEARER Child SO.
BACKHAUAL_ACTIVITY 90 SOMG_TX Work group confirmed the child so task closure
ROUTER_HUWAI_PROV 100 OSS_DEV MDD to Provision the CISCO Node
MAN_ROUTER_PROV 110 DATA_OPS MDD to Provision the CISCO Node
AUTO_HUWAI_PROV 120 OSS_DEV MDD to Provision the CISCO Node in MRTG
MAN_HUWAI_PROV 130 DATA_OPS MDD to Provision the CISCO Node
AUTO_DNS_PROVISION 140 OSS_DEV MDD to Provision the CISCO Node in MRTG
NETWORKING
MAN_DNS_PROVISION 150 MDD to Provision the CISCO Node
_OP
ADD_ELEMENT_IN_NM
160 DATA_OPS ADD ELEMENT IN NMS
NODE_CONFIG 170 ASOMG_DATA Link Description updation & configuration validation.
ANOC ATP 180 DATA_ANOC A ANOC AT&Reconciliation.
UPDATE INVENTORY 190 OSS_DEV Getting equipment into INSERVICE in Clarity.
RFS CHECK 200 O&M_ADN_A Ready For Service Provisioning
CLOSE SERVICE ORDER 210 OSS_DEV Closing Service Order.

9.6 CP_ACCESS_DATA_NFS ATTRIBUTES
Below is the list of attributes to be used for raising the CP_ACCESS_DATA_NFS SO.
ATTRIBUTE_NAME ATTRIBUTE_DEFAULTVALUE ATTRIBUTE_OPTIONALITY ATTRIBUTE_DESCRIPTION

SCR_ID NONE Scope Change Request ID
VLAN_ID1 CREATE VLAN ID1
RESEDENCIAL_VLAN CREATE VLAN ID2
CIRCUIT_SPEED N/A CREATE Circuit Speed
SERVICE_NUMBER N/A CREATE Service Number
NE_TYPE C35 CREATE Network Element Type
Parent BAN to which node
PARENTING_BAN CREATE
is allocated
NE_LOCATION NONE Network Location
NEW_NE_ID CREATE Network ID
NE_NAME NONE Network Element Name
APPROVAL_REFERENCE CREATE Project Plan No
NDD_REFERENCE_NO NONE NDD No for NE
CIRCLE CREATE Circle Attribute
IP Address of the
NE_IP_ADDRESS CREATE
EQUIPMENT
FACILITY_TYPE BN CREATE
RING_ID CREATE Ring ID
NAME_DEVICE_GROUP CREATE Name of City/Region
N_PE for C76,W60;U_PE
for
ROLE CREATE C35,C34,M37,W2D,W4D
AND PE_AGG for S37
Devices.
MNGT_VLAN VLAN127 CREATE MANAGEMENT VLAN
TYPE_OF_SERVICE N/A CREATE Type of Service
HOMING_DEVICE CREATE Homing device
BN_TYPE CREATE BN_TYPE
MACD_TYPE NONE MACD_TYPE
IGNORE_DISCOVERY_S IGNORE_DISCOVERY_STAT
NONE
TATUS US
DISCOVERY_MODE NONE DISCOVERY_MODE

OPERATION_TYPE NONE OPERATION_TYPE

UPLINK_INTERFACE NONE Uplink Interface Type
BACKHAUL SDH / PDH /
BACKHAUL N/A CREATE
IP RADIO / NA
RIL_IMT_MEN_DBEARER
BACKHAUL_SO NONE
Child SO Number.
BANDWIDTH NONE Bandwidth
HOMING_TOWN_FACI
NONE HOMING_TOWN_FACID
D
10.0 3G architecture for IBS locations
10.1 IBS Deployment Scenarios
1. IBS Sites on Fibre

a. SDH
b. 4E1 Opti-MUX/ Optical Modem
2. IBS Sites on Wireless
a. PDH Microwave
3. IBS Sites on Copper
a. Direct E1s (within 200-250 Mtrs. Copper Distance)
b. E1s via xDSL/ Long Reach E1s (beyond 250 Mtrs. Routing Distance)
Please Note- Any IBS sites not falling (or cannot be covered) under these planning guidelines
may please be discussed with FA Planning, NHQ.

2.0 Matrix- IBS Connectivity Solutions
IP
Backhaul
Delivery at Take
Case Media 2G 3G Backhaul Options Remarks
Node off /
Parenting
Site
Option-1
1.1 Fibre MEN Node on separate pair of
E1s
fibre
SDH (Direct)
Option-2
1.2 Fibre Ethernet Card- Plug-in the existing
SDH Equipment
E1s via Option-1
1.3 Fibre Back-to- Media Converter on Separate Pair
Back 4E1 of Fibre (if fibres are available)
Optical
Optical Option-2
Modems
Modem Free/ Unused E1s to be used (as
(4E1
1.4 Fibre 3E1s are spare)
Opti-
EoPDH CPE to be used in for IP Take off
MUX)
Backhaul or parent
site to be
E1s via
PDH Ethernet Card- Plug-in the existing MEN
2.1 Wireless PDH
Microwave PDH Radio RFS
Radio
(directly
Option-1 Option is
or IP
3.1 Copper Direct Ethernet (on CAT-5 Cable)- valid for
Radio or
within 90 Mtrs. distance locations
EoSDH)
within 200-
DLC or
Direct 250 Mtrs.
SDH - Option-2
E1s Routing
Direct E1 Additional E1s and EoPDH CPE
3.2 Copper distance
(Back-to-Back) to be used in for
from
IP Backhaul
Serving
Node
HDSL
Modem or New pair of Modem (Back-to-
Copper
DLC- Via E1s via Back) supporting E1 as well as
Distance not
3.3 Copper Long xDSL Ethernet (supports upto 11Mb/s
to exceed
Reach E1 Modem bandwidth upto 1KM)
500 mtrs.
(called E1-
ML)

11.0 Architecture of 3G services for 3G Non RNC locations:
Above digram is an example for Node-B connectivity with RNC.

3G non RNC locations will connect to RNC on E0-SDH connectivity. MEN L3 device i.e. ME
3810 is proposed as a aggregation device for aggregating the Node-B traffic. The Proposed ME
3800 will connect to TX. NE for carring the IUBs traffic.

RMEN - 3G IP Mobile Backhaul Architecture and Guidelines Ver0.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RMEN - 3G IP Mobile Backhaul Architecture and Guidelines Ver0.0

Uploaded by

Copyright:

Available Formats

RMEN 3G IP Mobile Backhaul Architecture & Guidelines

Reliance Mobile - 3G Services - A futuristic mobile experience

RMEN- 3G IP Mobile Backhaul

Reliance Communications Ltd (DAKC)

0 0 15-11-2010 NSMK/ HS/ PK NSMK/ HS/ PK Mr Ja la j Choud hri

Version Revision Date Made By Checked By Approved By

RMEN 3G Architecture Reliance Confidential

Page 1 of 69 Release V0.0

A printed copy of this document is considered uncontrolled

Copyright 2007 Reliance Communication Limited. All rights reserved.

RELIANCE INFOCOMM MAKES NO REPRESENTATION OR WARRANTY, EXPRESSED OR IMPLIED, WITH RESPECT TO

RMEN 3G Architecture Reliance Confidential

Page 2 of 69 Release V0.0

A printed copy of this document is considered uncontrolled

RMEN 3G Architecture Reliance Confidential

Page 3 of 69 Release V0.0

A printed copy of this document is considered uncontrolled

2 About This Design Document

Authors: Karunanithi NSM, Hemanshu Shah, Pramod P Kulkarni, Team NPEMEN

Approver: Sh Jalaj Choudhri

2.1 Document Purpose

2.2 Document Audience

Reliance Technical Team, Management and Authorized Vendors if any.

2.3 Document Usage Guidelines

This document consists of a number of components. These include

Network Backhaul Topology and Design

RMEN 3G Architecture Reliance Confidential

Page 4 of 69 Release V0.0

A printed copy of this document is considered uncontrolled

Network Security - Implemented best-practices security mechanisms across the network

Quality-of-Service - Traffic prioritization, Classes of Platinum, Gold, Silver, Best Effort of

RMEN 3G Architecture Reliance Confidential

Page 5 of 69 Release V0.0

A printed copy of this document is considered uncontrolled

4 3G-IP Mobile Backhaul Architecture

3G or 3rd Generation, is a generation of standards for mobile phones and mobile

RMEN 3G Architecture Reliance Confidential

Page 6 of 69 Release V0.0

A printed copy of this document is considered uncontrolled

4.2 Layer 3 MPLS VPN Deployment Model for 3G

Backhaul architecture on Metro is specifically designed to incorporate different vendors

Page 7 of 69 Release V0.0

A printed copy of this document is considered uncontrolled

- Network Topology describing Huawei RNC and NodeB

4.3 Network Topology - Huawei RNC & Node-B

RMEN 3G Architecture Reliance Confidential

Page 8 of 69 Release V0.0

A printed copy of this document is considered uncontrolled

4.3.1 Connectivity between Huawei M-2000 at RNC & MEN

4.4 Network Topology - ZTE RNC & Node-B

4.4.1 Network Topology - ZTE RNC & Node-B (Management)

RMEN 3G Architecture Reliance Confidential

Page 9 of 69 Release V0.0

A printed copy of this document is considered uncontrolled

4.4.2 Network Topology - ZTE RNC & Node-B (Service)

4.5 VLAN Assignments for Node-B Management and Services

4.5 .1 Management VLAN for Node-B

Management Vlan for both Huawei and ZTE Node-Bs VLAN 56

4.5 .2 Service VLAN for Node-Bs

RMEN 3G Architecture Reliance Confidential

Page 10 of 69 Release V0.0

A printed copy of this document is considered uncontrolled

4.6 VRF Attributes for Services and Management