TNG Standard Provisioning Process For CEN

TNG Standard Provisioning Process for CEN
Standard Provisioning Process for CEN
Prepared By: Reviewed By: Approved By: Version: Effective Date: Page:
0
Mr. Tushar Kataria Mr. Anil kumar Mr. Jijo Jhon 1.0 10-June-2016
Table of Contents
1. Introduction ........................................................................................................................ 3
1.1 Preface ....................................................................................................................... 3
1.2 Audience .................................................................................................................... 4
1.3 Scope and Requirements ........................................................................................... 4
1.4 Assumptions .............................................................................................................. 4
2. Executive Summary ............................................................................................................. 4
2.1 Overview .................................................................................................................... 5
2.2 CENv2 Network Overview.......................................................................................... 5
2.3 Network Topology ..................................................................................................... 7
2.4 CEN Devices.............................................................................................................. 15
2.5 Provisioning Pre-checks ........................................................................................... 16
2.6 Provisioning Utilization Pre-checks.......................................................................... 21
2.7 Provisioning Post-checks ......................................................................................... 24
3. CEN Provisioning Services & Configurations ..................................................................... 26
3.1 NLD Links (Point to Point on CEN). .......................................................................... 27
3.2 MPLS/ISP/ILP/SDH services (CEN + MPLS/ISP/ILP/SDH link) .................................. 33
3.3 Expressway link (Intercity links) .............................................................................. 36
1
3.4 PRI (Primary Rate Interface) .................................................................................... 39

3.5 Mobility (2G, 3G &4G) ............................................................................................. 48
4. CEN Load Balancing Solutions. .......................................................................................... 74
5. DSLAM Management ........................................................................................................ 75
5.1 Service Overview ..................................................................................................... 75
5.2 Access Topology ....................................................................................................... 76
5.3 Service Topology ...................................................................................................... 77
5.4 Service Resiliency ..................................................................................................... 81
2
1. Introduction
1.1 Preface
This document describes provisioning process for the CEN of the Bharti IP/MPLS Carrier
Ethernet Network which will be used as a common IP transport infrastructure that shall
cater to range of services such as Mobile Services & access technologies(2G, 3G, LTE), and
Enterprise Services(L2VPN, L3VPN). The overall design will cater to services (Data, Voice
and Video) for both Residential and Enterprise customers.
The document provides an insight on the provisioning process. It covers all aspects of this
network – the physical topology, protocol architectural overview and the respective
service descriptions. The purpose of this document is to provide as overview of
provisioning process. The document shall be used as a reference for services that are to be
deployed.
3
1.2 Audience
This document is intended for all personnel involved in the specification of requirements
for the proposed CENv2 Expansion (hardware, software and services) and for those who
are responsible for implementing and eventually operating the network. This document is
intended for use by Bharti CEN Team.
1.3 Scope and Requirements
The scope of this document is limited to the provisioning process of CEN. It covers Physical
Network Architecture Overview Provisioning Process.
1.4 Assumptions
The design presented in this document is based on the best information available at the
time of writing. It is assumed that reader of this document is familiar with Bharti
Requirements
2. Executive Summary
4
2.1 Overview
Bharti is deploying the converged network which will offer Voice, Video and Data services
to end users using different type of access technologies 2G, 3G, LTE, FTTH and Wi-Fi.
Every network is built to meet the business objectives, however the key differentiator is
the ability to adapt and support the inevitable changes in business dynamics. Ultimate goal
is to create a reliable, cost-effective and multi-faceted communications experience for
customer by providing seamless transformation over different types of IP/MPLS backhaul
access methods with a clear strategy of “any media to any end device”, Next-Gen
Architecture offering diverse service portfolios and IPv6 readiness on Day-1 to address
scalability and subscriber growth.
The overall design goals at Bharti CEN is to develop an end-to-end network architecture
that is highly available, secure and flexible enough to enable any mix of services. The
architecture must support a diverse portfolio of service offerings in order to effectively
enable the monetization of network resources, and must provide the ability for Bharti to
extend its services footprint to any point in the network as driven by business
requirements.
2.2 CENv2 Network Overview
The Bharti CEN is foundation of a secure, flexible and intelligent transport network for the
delivery of diverse services such as business VPN services, mobility services (2G, 3G & 4G)
along with residential and consumer oriented services such as IPTV and high speed
5
internet. Each service has varied architectural & Qos requirements, but leverages the
common network infrastructure to offer differentiated services.
The idea of moving 2G, 3G & LTE services from TDM & SDH infrastructure onto IP
infrastructure is at the core of this expansion. As the 2G/3G/LTE installed based is
migrated to IP, the IP infrastructure will need more resources in terms of ports,
bandwidth, routing memory, etc.
CEN network is a mix of 10G and 1G rings. In Aggregation and access network LSP are
designed as loose. While this approach provide more flexibility, traffic engineering is
required to ensure LSP from nodes in 10G ring should not take path through 1G rings.
BGP is a fundamental routing protocol in Airtel CEN network to signal reachability
information on VPNv4 addresses. As such, it is a vital component in offering any L3 service,
including MPLS/BGP VPNs. It is essential that the hierarchy, peering strategy, and general
parameter configurations be standardized in order to provide the highest level of stability,
scalability, and resilience. Rapid withdrawal will be used to fast convergence & Min route
advertisement will be adjusted in case of a node reboot so that only after a complete
reboot the node will then advertise the active routes into BGP/MBGP.
The purpose of Bharti CEN network is to aggregate intra-city traffic from various Access
networks for supporting various data, multimedia and next generation services. Also the
network will directly provide Ethernet based services to the Enterprise customers of the
company.
L2 VPN services will be configured on the routers to carry services from DSLAMs to BRAS,
ILP traffic and 2G backhaul from BTS to BSC.
6
L2 VPN services will be used for Layer 2 business VPNs, DSLAM management traffic, L2
aggregation on layer 3 VPN.
L3 VPN services (VPRN) will be used for business VPN services & Mobile backbone services.
2.3 Network Topology
7
From an IP perspective, the existing network topology has a three-tier

hierarchy of core, aggregation and access layers. Sub access layer has been
also been planned & are being implemented.
While NPE, Core and Aggregation network are built on High end router,
Access layer is deployed on low end routers. Nodes are connected in ring
over dark fiber. Wherever feasible Core nodes are connected over DWDM on
multiple links
Physical Network Topology

2.3.1 Core Layer
Core layer is planned and built on multiple 10GE rings connected over
DWDM network. However in small cities Core network will be
connected on 10G ring over dark fiber. Each of the core nodes is
8
protected either by a co-located redundant core router or by a router

deployed at nearest POP location. Aggregation rings are dual homed to
two core routers either deployed co-located or at geographically
dispersed location. For additional redundancy, depending on fiber
availability in region, full/partial mesh topology has been created. Core
routers are planned to work as pure “P” routers, however in certain
deployment scenario core router will act as NPE (Network Provide
Edge) router as well.
Core Network Topology
9
2.3.2 Aggregator Layer
In aggregation layer, nodes are connected on 10G ring over dark fiber.
Aggregation nodes are dual homed to the core routers. Depending on
the fiber topology, Parent core routers could be collocated or at
different locations. Some of the aggregation nodes are collocated with
Core Nodes.
10
Aggregation Network Topology
2.3.3 Access Layer
Access layer will have nodes connected on 1G/10G ring over dark
fiber. Depending on the fiber topology access ring will be either
terminated on a single Aggregator or dual homed to a pair of
11
aggregator. In certain deployments dual homed parent aggregator

nodes may not be the next hop peers.
Access Network Topology
2.3.4 Route Reflector
The Route-Reflector nodes are responsible for propagating all BGP routes between
core, Aggregator & Access (IPv4 & VPN-IPv4) routers using Multi-Protocol iBGP. Routes
learned from originating clients will be reflected to all other clients, thereby eliminating
the need for a full mesh of iBGP peering. Route-Reflectors store all IPv4 & VPN-IPv4
routes in their BGP tables. As the Route-Reflector plays such an integral role in the
control plane of the converged broadband network, it is a common and best practice
that the function is implemented on a dedicated router.
12
Route Reflector Topology
No user plane traffic passes through the Route-Reflector, as they

perform only control plane functions. As a result, there is no
requirement for the Route-Reflector to participate in any MPLS
signaling. RR will have connectivity with 2 Core/Agg nodes of CEN for
redundancy and IGP cost for links towards RR will be increased to
avoid RR to be part of IGP data path.
All the aggregation nodes are clients of both of these Route-
Reflectors for redundancy purpose. Beside that all the Aggregation
nodes are configured as in-line RR and all the access nodes are
configured as client of parent aggregation nodes.
13
Router Reflector Architecture
2.3.5 NPE
NPE is Network Provider Edge Router, deployed on the edge of CEN
towards service insertion point. For each critical service a pair of NPE
router has been designed and deployed and will connect to third
party equipment such as BRAS, ILP router, EPC etc. for insertion of
services in CEN network.
In the certain circumstances and for few of the services, NPE
functionality has been merged with Core and Aggregator routers of
CEN. This was the inherited practice in CEN network on Cisco
Platform and may applicable in some of the current deployment,
however that solely depends on the service scale and position of the
CEN router at service insertion point.
14
CEN diagram with NPE

2.4 CEN Devices
Bharti CEN Network is a combination of various routers (Cisco, Alcatel, Huawei & ZTE)
which are being deployed in the below cities -
NCR, Luckhnow, Chandigarh, Mohali & Hyderabad – Alcatel
Access Rings – SAR8, SAS-M, SAS-R, SRC-4,
Aggregator & Core Rings – ASR-12.
15
Coimbatore, Mumbai, Bhopal, Ahmedabad & Pune - Huawei.
In Pune ZTE routers are also being used.

Huawei Access, Aggregator & Core Rings – ATN & CX.
ZTE Access -ZXCTN 6220
Aggregators & Core – ZXCTN 9008
Chennai & Bangalore – Cisco
Access Rings – Cisco ASR 903, 6524, 7604 & 7603
Aggregator & Core Rings - Cisco ASR 9000
2.5 Provisioning Pre-checks
There are some pre checks which we have to perform for any RA to be provisioned.
 We have to check the NSDC comments for Vlan, A & B end router details.
 Check the router if it has free port available for provisioning, if not then dechoke the order
to planning for same & if vlan is not free reject the RA back to NSDC team to share a new
Vlan.
 Never use the below mentioned command on any of the Aggregator, NPE & Core routers.
 no l2vpn, no Xconnect group, no prefix-list, no prefix set.
 no router bgp , no ospf & no isis
 Always ensue that protection path is configured correctly.
16
 In case for Huawei need to check the primary & secondary aggregator correctly by
using
display cuurent-configuartion interface tunnels commands on router. Detailed info
is given in Section 3.1 & Section 3.6
 For Cisco & Alcatel, NSDC team will share handover details (NPE or Aggregator) &
services are to be dropped directly on them.
 Bandwidth Utilization has to be checked for any order above 500 Mb, refer Section 2.6 for
further details.
 For Huawei WiFi services should be configured to NPE/Core routers via aggregator only,
refer Section 5.6 for detailed configuration. PFB WiFi configuration template.
17
 Now open the order in Supplement mode to check the Label & Field Values which
should also show the A& B end router details in A21 & B11 field.
18
19
20
 Check C1 & C11 values for Bandwidth requirements.

 After this make a template in notepad file with complete configurations, check the BW
policy to be applied on the interface.
 Once configuration is done on the router, update the E13, E14, F11 & F12 with device &
port details respectively.
 For utilization guidelines check section 2.5
Before closing the RA we have to update the A23 value selecting CEN from dropdown menu.
2.6 Bandwidth Utilization Pre-checks
Guidelines for Provisioning
21
Access:
 For Shared Rings, Max Capacity cap on a single customer order to be restricted to 20%
of the ring capacity. Order to be moved to planning for ring upgrade should the single
order capacity exceed 20% of the installed ring capacity
 For Shared Rings, any order with capacities >20% of installed ring capacity to be
declared “feasible subject to ring upgrades” during feasibility irrespective of ring
utilization.
 For Shared Rings, Provisioning of B2B orders with Capacity >5% of the installed ring
capacity to be stopped at 50% peak Ring Utilization
 For Shared Rings, Provisioning for B2B orders with capacities <=5% can be continued till
such time the peak ring utilization reaches 80%
 For Shared Rings, Complete stop on provisioning for all types of orders at 80% peak ring
utilization
 Upgrade trigger at 70% peak utilization of the ring (Planning Specific)
 A 2nd stack will be deployed as a part of upgrade and will be used only for high capacity
B2B deliveries which have been defined as “CAC Enabled Rings”. Existing high capacity
links (>= 1 Gig) will be migrated from Stack1 to stack 2. CAC will be defined on the
Stack2 for guaranteed/nearly guaranteed capacities.
 No provisioning Cap on CAC Enabled rings except that upgrade trigger will be at 70%.
Aggregate:
 For Shared Rings, Provisioning of B2B orders with Capacity >5% of the installed ring
capacity to be stopped at 50% peak Ring Utilization
22
 For Shared Rings, any order with capacities >20% of installed ring capacity to be
declared “feasible subject to ring upgrades” during feasibility irrespective of ring
utilization
 For Shared Rings, Provisioning for B2B orders with capacities <=5% can be continued till
such time the peak ring utilization reaches 80%
 For Shared Rings, Complete stop on provisioning for all types of orders at 80% peak ring
utilization
 Upgrade trigger at 50% peak utilization of the ring (Planning Specific)
 A 2nd stack will be deployed as a part of upgrade and will be used only for high capacity
B2B deliveries which have been defined as “CAC Enabled Rings”. Existing high capacity
links (>= 1 Gig) will be migrated from Stack1 to stack 2. CAC will be defined on the
Stack2 for guaranteed/nearly guaranteed capacities.
 No Provisioning Cap on CAC Enabled rings except that upgrade trigger will be at 80%.
NNI:
 For EPT-CEN Provisioning will be Utilization based. Utilization to be monitored and
triggered by Traffic Engineering at 50% peak utilization.
 Packet Network-Packet Network NNIs are to be 10Gigs with a few exceptions based on
traffic patterns.
 Provisioning has to be stopped on NNIs once the utilization of the NNI reaches 80%
(Applicable only for Packet-Packet NNIs).
23
2.7 Provisioning Post-checks
We need to check the below points after provisioning has been completed.
 Description format for interfaces as per below standard. This format to be applied on all
the interfaces at Access port & on the Aggregator end NNI subintefaces or on main port
as per details shared.
## RA Number - Circuit ID - Customer Name - BW – Date##
 Need to ensure protection path is configured correctly as it may lead to outage if

primary path goes down
In case for Huawei need to check the primary & secondary aggregator correctly by using
display cuurent-configuartion interface tunnels commands on router.
For Cisco & Alcatel, NSDC team will share handover details (NPE or Aggregator) &
services are to be dropped directly on them.
 We also need to check the MTU which are defined as per devices & service standard.
 For Cisco – MTU should be like below :
 ASR9K <—> MTU 9216<—>ASR9K
 ASR9K (MTU 9216) <—> (MTU 9202)7600 (IOS) / (9202) ASR903
 7600 Access (MTU9202) <—>7600 (Access 9202).
24
 For Alcatel –
 For any router Port MTU should be 9212 & service MTU should be less than port
(MTU=9014)
 On some ports MTU 9212 is not acceptable, so port MTU should be 2102 &
service MTU would be 1514.
 For Huawei –
 Jumbo MTU size is 9500 to be enable on both end
 For Expressway links (include Multivendor devices) –

 For Cisco & Huawei both end MTU should be 9212.
 For Cisco & Alcatel – Cisco should be 9000 & Alcatel should be 9014
 For Alcatel & Huawei – Alcatel should be 9014 & Huawei should be 9000
 SDP checks to be done in Alcatel devices –

 If any route is learnt via ISIS (x.x.x.x/32) then we will have to create SDP as LDP
base.
 If any route is learnt via BGP (x.x.x.x/32) then SDP will be created on BGP base.
 If any route is learnt as unknown then SDP will be crated on BGP base(Depends on
router version)
o SAR 8 Router – we will use advertise label ipv4 command in BGP for
aggregator & on Aggregator perform command – advertise label ipv4
include ldp prefix.
o SAS R – use advertise label ipv4 use SVC router command in BGP
25
 Interface & Vlan are configured as per design comments, BW is configured correctly.
 For Cisco, Chennai services are to be made on loopback 0 & for Bangalore loopback 1
has to be used.
 For Alcatel & Huawei , loopback 0 has to be used.
3. CEN Provisioning Services & Configurations
Different services are being deployed in CEN Domain.

These include L2 services for NLD links (point to point), MPLS Links (CEN + MPLS
services), ISP links (CEN + ISP services), ANG links (CEN + SDH services), and Expressway
links (intercity links)
These are various L3 services for Mobility (3G & 4G) & DSLAM services.
2G services are also being deployed over CEN through PRI Configuration.
26
3.1 NLD Links (Point to Point on CEN).
NLD links are point to point links which drop end to end on CEN devices only. Customer
end devices are directly connected or dropped on CEN routers
Epipe is a point-to-point Ethernet bridging service that forwards traffic from one
customer site to another. When Epipe is required between two sites, only one
pseudowire (PW) is required and one Service Access Point (SAP) or customer-facing port
is required on each PE routers.
A Service Access Point (SAP) is an identifying label for network endpoints used in Open
Systems Interconnection (OSI) networking. The SAP is a conceptual location at which
one OSI layer can request the services of another OSI layer.
27
Configuration of NLD links- point to point link b/w two access routers
3.1.1 Alcatel Router
Alcatel Router -
Router A-
#configure port 1/5/3
Description "FTTB#CKT ID#B/W#RA number#Date of Provisioning"
#ethernet
mtu 9212
egress-rate B/W kbps
ingress-rate B/W Mbps cbs 100 kilobytes
exit
exit
no shutdown
#Configure service epipe 1274(epipe ID) customer 1 create

description "FTTB#CKT ID#B/W#RA number#Date of Provisioning"
service-mtu 9014
28
service-name "FTTB#CKT ID#B/W#RA number#Date Of Provisioning"

#sap 1/5/3 create
description "mtu_description"
exit
spoke-sdp 406(Far end SDP):1274(Epipe ID) create
exit
no shutdown
Router B-
#configure port 1/5/3
#ethernet
mtu 9212
exit
exit
no shutdown
service-mtu 9014
#sap 1/5/3 create
29
exit
spoke-sdp 406(Far end SDP):1274(Epipe ID) create
exit
no shutdown
3.1.2 Cisco Router
A END - 10.230.1.196
interface Gig0/3/0
description ##1415627##BLTU-ANG00338##LIMRAS ERONET BROADBAND SERVICE PVT
LTD##15092015#20MB##
service instance 2080 ethernet
encapsulation dot1q 2080
service-policy input 20Mb
service-policy ouput 20Mb
xconnect 125.62.173.41 100002080 encapsulation mpls

---------------------------------------
Policy Map 20Mb
Class class-default
police cir 20480000 bc 3840000 conform-action transmit exceed-action drop
30
B END - 125.62.173.41
interface Gig0/2/0
description ##1415627##BLTU-ANG00338##LIMRAS ERONET BROADBAND SERVICE PVT
LTD##15092015#20MB##
service instance 2080 ethernet
encapsulation dot1q 2080
service-policy input 20Mb
service-policy ouput 20Mb
xconnect 10.230.1.196 100002080 encapsulation mpls
------------------------------------------
Policy Map 20Mb
Class class-default
police cir 20480000 bc 3840000 conform-action transmit exceed-action drop
3.1.3 Huawei Router

A end- 10.229.98.31
interface GigabitEthernet0/1/7
description FTTB-LL#L2-MSPW#MOBYLL#BALW-
ANG02715#14Mbps#1352735#03072015#<MUM_MIN_901_AC1_HAT950BR060
mpls l2vc 10.25.1.7 312402 tunnel-policy hvpn -  Primary Path
mpls l2vc 10.25.1.8 5312402 tunnel-policy hvpn secondary Protection Path
qos-profile p7 inbound
port shaping 14
31
-------------------------------------------------------------------------------------------------------
A end- Primary Aggregator - 10.25.1.7
mpls switch-l2vc 10.229.98.31 312402 tunnel-policy hvpn between 10.229.77.57 312402
tunnel-policy hvpn encapsulation ethernet
A end – Secondary Aggregator - 10.25.1.8
mpls switch-l2vc 10.229.98.31 5312402 tunnel-policy hvpn between 10.229.94.129
5312402 tunnel-policy hvpn encapsulation ethernet
---------------------------------------------------------------------------
B end- 10.229.77.240
interface GigabitEthernet0/2/4
description FTTB-LL#L2-MSPW#MOBYLL#BALW-
ANG02715#14Mbps#1352735#03072015#MUM_BUS_901_1AC_HAT950BR104
mpls l2vc 10.229.77.57 312402 tunnel-policy hvpn  Primary Path
mpls l2vc 10.229.94.129 5312402 tunnel-policy hvpn secondary Protection Path
qos-profile p8 inbound
port shaping 14
B end- Primary Aggregator - 10.229.77.57

B end- Secondary Aggregator - 10.229.94.129

32
3.2 MPLS/ISP/ILP/SDH services (CEN + MPLS/ISP/ILP/SDH link)
These link are a combination of CEN & other technologies like MPLS, ISP & SDH.
The NSDC team will submit the design details with CEN + MPLS POI details, CEN access
end details will also be shared by NSDC team & a specific vlan will be given to used b/w
CEN + MPLS/ISP NNI handover point .
Below is the configuration template –
Alcatel Router
33
CEN Access Router –
#Configure port 1/5/2

description "FTTB#CKT ID#B/W#RA number#Date Of Provisioning"
ethernet
# mtu 9212
exit
exit
no shutdown
Configure service epipe 1174(epipe ID) customer 1 create

service-mtu 9014
endpoint "FTTB" create
revert-time 1
standby-signaling-master
exit
sap 1/5/2 create
exit
spoke-sdp Secondary NPE SDP:Epipe ID endpoint "FTTB" create ----> Protection
Path
34
precedence 2
exit
spoke-sdp Primary NPE SDP: Epipe ID endpoint "FTTB" create
precedence primary
exit
no shutdown
CEN NPE router having NNI with MPLS/ISP/SDH
NPE-1/2
service-mtu 9014
sap lag-11(H/O with ISP/MPLS):2217 (Vlan) create
exit
spoke-sdp 324(Access Sdp):1174(Epipe ID) create
no shutdown
exit
no shutdown
NPE-2/2
35
service-mtu 9014
sap lag-11(H/O with ISP/MPLS):2217 (Vlan) create
exit
spoke-sdp 324(Access Sdp):1174(Epipe ID) create
no shutdown
exit
no shutdown
3.3 Expressway link (Intercity links)
These links are provisioned for customers requiring connections b/w 2 different cities.
NSDC team (Design team to share the exact requirement).
This can be either CEN to CEN link or maybe dropped on SDH handover points which will
carry the traffic further.
We need to stich the l2circuit on the ring aggregator & from aggregator the stitching
would be done for the other end aggregator which is different city.
The IP address of the both end Aggregator have to passed in the Core routers which is
having a direction connectivity with other end Core router.
36
Alcatel Router –
Access
configure port 1/1/1
description "FTTB-LL#L2-P2P#P2PLL#UIDA-
ANG00026#540Mbps#1032456#15092015#192.168.8.47"
ethernet
mode access
access
exit
mtu 9212
egress-rate 552960
exit
no shutdown
--------------
configure service epipe 2457 create customer 1
37
ANG00026#540Mbps#1032456#15092015#192.168.8.47"
service-name "FTTB-LL#L2-P2P#P2PLL#UIDA-
ANG00026#540Mbps#1032456#15092015#192.168.8.47"
endpoint "P2P" create
revert-time 1
exit
sap 1/1/1 create
exit
spoke-sdp 847:2457 endpoint "P2P" create
precedence primary
no shutdown
exit
no shutdown
------------------------
Aggregator side-
configure service epipe 2457 customer 1 vc-switching create
38
ANG00026#450Mbps#1032456#15092015#192.168.8.47"
spoke-sdp 30:2457 create

no shutdown
exit
no shutdown
exit
no shutdown
Note- Same configuration to done from other end.
3.4 PRI (Primary Rate Interface)
The Primary Rate Interface (PRI) is a telecommunications interface standard used

on an Integrated Services Digital Network (ISDN) for carrying multiple DS0 voice
and data transmissions between the network and a user. PRI is the standard for
providing telecommunication services to offices.
Alcatel –
39
The format of the label for SDH and/or SONET TDM-LSR is:
0 1 2 3
01234567890123456789012345678901
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| S | U | K | L | M |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
For SONET, the signaling scheme is used in order to provide easy interworking
between
SDH and SONET signaling. For the S field a STS-3 group, which corresponds with
the SDH AUG-1 level is introduce. The U field indicates the position of the STS-3c-
SPE or STS-1-SPE within the STS-3 group
Below is the configuration for same –

First of all we have map the KLM configuration which is common for Electrical &
Ethernet
Unframed KLM
configure port aps-5
sonet-sdh
path sts3
no shutdown
exit
40
group tug3-1 payload vt2

path vt2-1.1.1
no shutdown
exit
tdm
e1 1.1.1
framing e1-unframed
channel-group 1
encap-type cem
no shutdown
exit
no shutdown
exit
If Last mile is electrical drop (G.703)
NPE
configure service cpipe 4869 customer 6 vc-type satop-e1 create
description "PRI#Customer nameY#OREDER ID#Date Of Provisioning"
service-mtu 1500
service-name "PRI#Customer nameY#OREDER ID#Date Of Provisioning"
41
sap aps-5.1.1.1.1 (KLM-111) create

ingress
qos 333
exit
egress
qos 333
exit
exit
exit
no shutdown
Access
configure service cpipe 4869 customer 6 vc-type satop-e1 create
service-mtu 1500
sap 1/3/1.1 create
ingress
qos 333
exit
egress
qos 333
exit
exit
42

exit
no shutdown
If last mile is Ethernet Drop
NPE
configure service epipe 2113 customer 1 create
service-mtu 1500
sap aps-5.1.6.3.1 create
cem
local-ecid 163
remote-ecid 163
remote-mac 18:4a:6f:24:82:42(customer end mac)
exit
exit
exit
no shutdown
Access
43

service-mtu 1500
sap lag-4:2113(Vlan) create
exit
exit
no shutdown
Huawei
44
A end IP - 10.229.96.188 Port S0/3/0:0

B end- 10.229.98.76- port 0/3/1-0/4/1- interface Trunk-Serial 3/52:0 (KLM 143) (SDH –CEN
HANDOVER )
--------------------------------------------------------
A End- 10.229.96.188
interface S0/3/0:0
link-protocol tdm
y
description PRI#L2-MSPW#CKT_ID_TMPA1_637489#2Mbps#RA-17109764#MEDFIELD
RESEARCH AND ADVISORY PVT LTD
mpls l2vc 10.229.77.51 pw-template tdm 17109764
mpls l2vc 10.229.77.66 pw-template tdm 517109764 secondary
mpls l2vpn oam-mapping
mpls l2vpn redundancy master
mpls l2vpn reroute delay 300
45
mpls l2vpn stream-dual-receiving

#
agg--1-10.229.77.51
-----------------------------------------------------------------------------------------------------------------------------
-------------
17109764 tunnel-policy hvpn encapsulation satop-e1 control-word-transparent
--------------------------------------------------------------------------------------------------
agg-2- 10.229.77.66
-----------------------------------------------------------------------------------------------------------------------------
-------------
--------------------------------------------------------------------------------------------------
B End- 10.229.98.76
interface Trunk-Serial 3/52:0
46
link-protocol tdm
y
description PRI#L2-MSPW#CKT_ID_TMPA1_637489#2Mbps#RA-17109764#MEDFIELD
RESEARCH AND ADVISORY PVT LTD
mpls l2vc 10.229.77.31 pw-template tdm 17109764
mpls l2vc 10.229.77.46 pw-template tdm 517109764 secondary
mpls l2vpn oam-mapping
mpls l2vpn redundancy master
mpls l2vpn reroute delay 300
mpls l2vpn stream-dual-receiving
#
-----------------------------
agg-1- 10.229.77.31
------------------------------------------------------------------------------------------
tunnel-policy hvpn encapsulation satop-e1 control-word-transparent
47
--------------------------------------------------------------------------------------------------
agg-2-10.229.77.46
-----------------------------------------------------------------------------------------------------------------------------
------------------------
Cisco
3.5 Mobility (2G, 3G &4G)
Mobility services are having different configuration for different regions.
There are different interfaces that is used for carrying different traffic, as in the case of
2G technology GBoIP interface is used for carrying Signaling and data traffic and in the
case 3G technology IUPS interface is used for carrying Signaling and data traffic.
2G and 3G traffic will be transparently carried over L2 VPN (VPWS) in Pseudowire
architecture. In these Pseudowire architecture two options are possible.
Option 1: If RNC/BSC is connected to the CEN access router then Multisegment Epipe
will be created between end points of CEN (Access and NPE routers) to carry 2G and 3G
traffic.
48
Option 2: If RNC/BSC is connected to the CEN Agg/core router then single segment
Epipe will be created between end points of CEN (Agg/core and NPE routers) to carry 2G
and 3G traffic
RNC/BSC traffic from MPBN Router will be carried over as Epipe service in single/multi-
segment pseudowire originating on Access router & terminating on Aggregation and
originated from Aggregation and terminated in NPE routers connected to SGSN Router.
Three Epipe will be created, first for carrying signaling and data traffic( GBoIP) of
2G,second for carrying data traffic (IUPS-UP) of 3G and third for carrying signaling traffic
49
(IUPS-CP) of 3G and these three Epipe will be created only from those
access/aggregation/core router where MPBN router will be connected and behind that
RNC/BSC will be connected.
We will start with 2G services.
 2G service on L2 circuit
We have to configure APS group on STM for further KLM configuration. This is a one-
time requirement.
Automatic Protection Switching (APS) is used to create a fault
tolerant topology by configuring a primary and secondary path for each VLAN.
The simplest class of mechanism for network survivability in the event of failure on a
network element or link is automatic protection switching (APS). APS schemes involve
reserving a protection channel (dedicated or shared) with the same capacity as the
channel or facility to be protected. This white paper provides an overview of the
different types of protection switching available with SONET/SDH networks, focusing on
50
technologies that automatically work at the level of either the SONET (SDH) Line
(Multiplex Section) or Path.
Cpipe is the VPWS (Virtual Private Wire Service) service that is used to carry
TDM frames b/w two nodes on IP/MPLS network. It is a point to point VPN
service that emulated a TDM leased line
VPRN (Virtual Private Routed Network) is a Multipoint-to-Multiponit Layer 3 VPN

Service of Alcatel-Lucent. It can be imagined like a router. So, in this service,
routing is the main point. With VPRN, multiple sites of the customer can connect
over an IP/MPLS network
Configuration -
APS GROUP
aps
switching-mode uni-1plus1
working-circuit 1/3/1
protect-circuit 1/4/1
exit
sonet-sdh
path sts3
no shutdown
exit
51

path vt2-1.1.1
no shutdown
exit
path vt2-1.1.2
no shutdown
exit
path vt2-1.1.3
no shutdown
exit
tdm
e1 1.1.1
framing e1-unframed
channel-group 1
encap-type cem
no shutdown
exit
no shutdown
exit
e1 1.1.2
framing e1-unframed
channel-group 1
encap-type cem
52
no shutdown
exit
no shutdown
exit
e1 1.1.3
framing e1-unframed
channel-group 1
encap-type cem
no shutdown
exit
no shutdown
exit
END –A:-access – Handover point for customer
cpipe 2331 customer 6 vc-type satop-e1 create

description "2G#MOBY2G#L2-P2P#BCLD-
ANG58044#2Mbps#1523928#01032016"
service-mtu 1500
service-name "MOBY2G#BCLD-ANG58044#2Mbps#1523928#01032016"
ingress
qos 333
exit
53
egress
qos 333
exit
exit
exit
no shutdown
exit
END-B:-NPE – Handover to BSC
cpipe 2331 customer 6 vc-type satop-e1 create

description "2G#MOBY2G#L2-P2P#BCLD-
ANG58044#2Mbps#1523928#01032016"
service-mtu 1500
service-name "MOBY2G#BCLD-ANG58045#2Mbps#1523928#01032016"
ingress
qos 333
exit
egress
qos 333
exit
exit
54
exit
no shutdown
exit
 2Gservice on L3 Chandigarh
Alcatel Router –
First of all we have to create a vprn number 200001, this is common for 2G
configuration in Chandigarh only on Access router
Below is the policy to be applied on Router before configuring the service.

RT values should be exactly same as marked below in Red to make the services
Access Router configuration
END A -
config router policy-option
begin
community "CHD-2G-ABIS-C34-1" members "target:65111:702"
community "CHD-2G-ABIS-C34-2" members "target:65111:802"
policy-statement "EXPORT-CHD-2G-ABIS-C34"
entry 10
from
protocol direct
55
exit
action accept
community add "CHD-2G-ABIS-C34-1"
exit
exit
default-action reject
exit
policy-statement "IMPORT-CHD-2G-ABIS-C34"
entry 10
from
protocol bgp-vpn
community "CHD-2G-ABIS-C34-2"
exit
action accept
exit
exit
exit
commit
configure service vprn 200001 customer 1 create

description "FDD-OAM"
vrf-import "IMPORT-CHD-2G-ABIS-C34"
vrf-export "EXPORT-CHD-2G-ABIS-C34"
56
autonomous-system 65111
route-distinguisher 10.228.222.175:201
auto-bind ldp
interface "TRAF-LCL-1" create
description "2G-LCL#L3ONMHS#MOBY2G#BMLM-
ANG15469#8MB#1432583#22092015#N2CHDACC25XXXACR001"
address 10.135.184.126/30
ip-mtu 1500
sap 1/5/7:132 create
exit
exit
interface "TRAF-RMT-1" create
description "2G-RMT#L3ONMHS#MOBY2G#BMLM-
ANG15470#60MB#1432583#22092015#N2CHDACC25XXXACR001"
address 10.135.69.46/28
ip-mtu 1500
exit
exit
service-name "FDD-OAM"
no shutdown
 3G service on L2
57
Alcatel Router
For Multi Chassis Configuration for SASM – This is basically combining 2 ports of
different router to act as one.
MC-LAG is a proprietary solution which allows link aggregation between multiple

devices (chassis).The CE device is completely unaware that its Ethernet links that belong
to the same LAG (Ether channel in Cisco) are connected to two (ALU supports upto
4 devices in MC-LAG) separate PE devices. The two PE routers each have one LAG
connected to the same CE device. At a time, only one PE router's LAG ports are active
and carrying traffic. The other PE router's LAG ports are standby and only become active
when failure is detected in the active links. The PE routers perform election to decide
the active and standby router.
58
We will configure 1 port each on 2 different router can be same or different, create 1
epipe which can have same values or different
Access Router
End A –

description "3G-IBS#BCLD-ANG58407#1543210#16Mbps#02162016#RNC-VKP04"
ethernet
59
mode access
access
exit
encap-type dot1q
mtu 9212
speed 100
exit
no shutdown
********************************************************************
service-mtu 9014
endpoint "IBS" create
revert-time 1
exit

exit
spoke-sdp 85:2404 endpoint "IBS" vc-type vlan create
precedence primary
exit
precedence 1
exit
60
no shutdown
***********************************************************
Access Router –
END B -

ethernet
mode access
access
exit
encap-type dot1q
mtu 9212
speed 100
exit
no shutdown
************************************************
service-mtu 9014
endpoint "IBS" create
61
revert-time 1
exit

exit
precedence primary
exit
precedence 1
exit
no shutdown
***********************************************************************
NPE: ---
Aggregator End
configure service vpls 2400 customer 1 create

service-mtu 9014
send-flush-on-failure
split-horizon-group "IBS" create
exit
62
stp
shutdown
exit
service-name "IBS-Data-2404"
ingress
qos 10
exit
exit
spoke-sdp 1397:2454 split-horizon-group "IBS" vc-type vlan create
no shutdown
exit
no shutdown
--------------------
configure service vpls 2450 customer 1 create
service-mtu 9014
send-flush-on-failure
split-horizon-group "IBS" create
exit
stp
shutdown
exit
63
service-name "IBS-Data-2450"
ingress
qos 10
exit
exit
spoke-sdp 6622:2450 split-horizon-group "IBS" vc-type vlan create

no shutdown
exit
no shutdown
 3G service on L3
This service is a L3 VPN solution where we need to configure port as remote or local, as
per the
requirement.
Need to create 2 VPRN circuit 500001 & 600001, assign the specific ports under them
GURGAON (NCR)
Remote Port – For Traffic
64
Configure port 1/6/6

description "3G#VPRN#LTE#BCLD-CEN-
28609#80Mbps#1225889#29012015#GRG_GUV_901_1NP"
ethernet
encap-type dot1q
egress-rate 80000(B/W kbps)

ingress-rate 80 cbs 100 kilobytes
exit
exit
no shutdown
exit all
Local Port – For Management
Configure port 1/5/6
description "3G#VPRN#LTE#BCLD-
ANG56742#21Mbps#1488624#20112015#GRG_GUV_901_1NP"
ethernet
encap-type dot1q
egress-rate 21504
65
ingress-rate 21 cbs 100 kilobytes

exit
exit
no shutdown
exit all
STEP 2:-
Configure router policy-options

begin
configure router policy-options

begin
community "lub_GRG_H_1" members "target:65111:913"
community "lub_GRG_H_2" members "target:65111:917"
community "lub_GRG_S_1" members "target:65111:914"
community "mub_GRG_H_1" members "target:65111:915"
community "mub_GRG_S_1" members "target:65111:916"
policy-statement "EXPORT-GRG-lub"
entry 30
66
from
protocol direct
exit
action accept
community add "lub_GRG_S_2"
exit
exit

policy-statement "EXPORT-GRG-lub"
entry 30
from
protocol direct
exit
action accept
community add "lub_GRG_S_2"
exit
exit
entry 40
67
from
exit
exit
exit
policy-statement "EXPORT-GRG-mub"
entry 30
from
protocol direct
exit
action accept
community add "mub_GRG_S_2"
exit
exit
exit
policy-statement "IMPORT-GRG-lub"
entry 40
from
protocol bgp-vpn
community "lub_GRG_H_1"
exit
action accept
exit
68
exit
exit
policy-statement "IMPORT-GRG-mub"
entry 40
from
protocol bgp-vpn
community "mub_GRG_H_1"
exit
action accept
exit
exit
exit
commit
exit all
------------------------------------------------------
STEP 3:-
Configure services
customer 1 create
description "Default customer"
exit
customer 2 create
69
description "Telecom_Traffic"
exit
customer 3 create
description "OAM-Traffic"
exit
customer 4 create
description "MW-DCN-Traffic"
exit
customer 5 create
description "CP-Traffic"
exit
customer 6 create
description "2G-Traffic"
exit
exit all
-------------------------------------------------------------------
config service vprn 500001 customer 1 create
description "IUB-TRAFFIC"
vrf-import "IMPORT-GRG-lub"
vrf-export "EXPORT-GRG-lub"
auto-bind ldp
70
interface "lub_673_Rmt" create

description "3G-IUB-RMT#L3IUBHS#MOBY3G#BCLD-
address 10.160.227.65/29
ip-mtu 1500
exit
sap 1/6/6:2417 ingress qos 111
sap 1/6/6:2417 egress qos 111
exit
exit
interface "lub_673_LCL" create
description "3G-IUB-RMT#L3IUBHS#MOBY3G#BCLD-
address 10.160.155.33/30
ip-mtu 1500
exit
exit
exit
no shutdown
71
exit all
-------------------------------------------------------------------------------
config service vprn 600001 customer 1 create
description "mub"
vrf-import "IMPORT-GRG-mub"
vrf-export "EXPORT-GRG-mub"
auto-bind ldp
interface "mub_673_Rmt" create
description "3G-MUB-RMT#L3MUBHS#MOBY3G#BCLD-
address 10.195.77.65/29
ip-mtu 1500
exit
exit
exit
interface "mub_673_LCL" create
description "3G-MUB-RMT#L3MUBHS#MOBY3G#BCLD-
ANG56743#21Mbps#1488624#20112015GRG_GUV_901_1NP"
address 10.195.71.33/30
ip-mtu 1500
72

exit
exit
no shutdown
exit
no shut
exit all
3.6 CEN Configuration Templates (Alcatel, Huawei, Cisco)
Below is the configuration file for all Alcatel Routers
ALCATEL
TEMPLATE.docx
Below is the configuration file for all Huawei Routers
Huawei
Templates.docx
Below is the configuration file for all Cisco Routers
73
Cisco Mobility Cisco B2B.docx

Templates.docx
4. CEN Load Balancing Solutions.
Bharti CEN has multiple paths in the core ring and pseudowire (MPLS L2 VPN) traffic
pass through the core ring, then in the core ring all traffic for this pseudowire takes the
same path. We do not see load-balance of. PW traffic like we see when traffic is MPLS
L3 VPN.
To implement load balancing for MPLS L2 VPN we need to perform the below mention
solution (vendor based) so that traffic can load balance.
This solution has to be implemented for all link having BW 500 MB & above.
For Cisco FAT PW solution has to be implemented for all circuits except for expressway
74
For Alcatel Hash Label solution has to be implemented for all circuits except
expressway.
For Huawei, we are already using the stitching technique, where all circuits are being
provisioned via aggregator so any other specific solution is unavailable for load
balancing.
The circuit is automatically load balanced through tunnels which are already
implemented on all routers
5. DSLAM Management
5.1 Service Overview
Bharti Airtel has a multi-vendor DSLAM deployed in network. All these DSLAMs are
managed by respective EMS deployed at centralized location. DSLAM Management
traffic is carried over CEN either using VPLS or using layer-3 VPN services. Different
VLAN ID is allocated for each DSLAM vendor for management traffic.
75
5.2 Access Topology
There are two types of topologies for connecting DSLAM to CEN access network
1. DSLAM are connected to CEN access box on 1G copper link

2. Ring of MSAN is terminated on a pair of CEN access box on 1G fiber link
76
5.3 Service Topology
Multiple DSLAMs will connect to the CEN access or sub access node. For simplicity
DSLAM design is shown and similar service design topology will be used for all vendors
DSLAM management as well. Depending on management IP pools, either L2 or L3 will
be used for carrying DSLAM Management traffic over CEN.
L2 based Solution
As shown in the figure below, multiple DSLAMs will connect to the CEN access router.
DSLAM will have in-band management and the management is isolated by the VLAN-ID.
On the access router, L2 PW per DSLAM type will be configured with PW redundancy
till the nearest aggregation routers. Aggregation routers in turn will have full mesh L2
connectivity with other Aggregation & NPE routers providing an end-to-end L2 solution
with better scaling & service management.
At the NPE side, management switch connects to the NPE router in a dual homed
topology. In order to provide chassis level redundancy, bundling will be used at the NPE
side connectivity.
77
Mentioned below are the control plane characteristics of the service topology shown in
figure
1. L2 service per DSLAM vendor will be configured on Access routers with PW redundancy
having dot1q sap configured with the defined VLAN for DSLAM management
2. L2 on Access routers is configured which terminates on parent aggregation routers. One

PW is configured as active & other as backup. Only one PW will be active at a time, thus
avoiding any loop scenario between Access & aggregation nodes.
3. A full Mesh of L2 is configured per DSLAM vendor between aggregation & NPE routers
providing an end-to-end L2 solution.
4. NPE routers are configured with a dot1q towards the management switch with the Vlan
defined for DSLAM management.
78
5. Bundling will be configured on NPE routers for providing link and node level redundancy
for management switch connectivity.
6. Normal Bundling is configured on management switch with dual homed links to NPE
routers.
7. T-LDP signaling is used to signal the L2 service.
8. Transport protocol used between Access & NPE routers will be LDPoRSVP
L3 based Solution
As shown in the figure below, multiple DSLAMs will connect to the CEN access router.
For simplicity only single DSLAM design is shown, similar service design topology is
used for other vendors DSLAM management. DSLAM will have in-band management
and the management is isolated by the VLAN-ID.
On the Access & NPE routers one L3VPN per DSLAM vendor will be created for the
management of the DSLAMs. At the NPE side, DSLAM management network is
connected to the NPE router in a dual homed topology.
79
1. L3VPN Hub & Spoke service per DSLAM vendor will be configured on Aggregation
routers with dot1q configured with the defined VLAN (for DSLAM management in
Access Router.
80
2. Route-Reflectors will provide the control plane route exchange between Access
routers & NPE routers connecting the DSLAM Manger network
3. Static route will be used as the PE-CE protocol for all VPN.
4. At Hub Site VPN will import HUB & Spoke RT and export HUB RT, while Spoke sites will
import HUB RT & export Spoke RT
5.4 Service Resiliency


1. Link failure in the Core, Aggregation or Access ring
 Any link failure in the core, aggregation or access ring triggers the RSVP-TE facility
backup
 Traffic switches to the backup LSP within sub-50 ms
2. Active port/s goes down on management switch
 Active port between management switch & NPE router goes down triggering the
standby port on management switch to start accepting management Traffic.
 A mac-flush is sent by the NPE router within the L2 service towards the other PE
routers to flush the mac table entries learnt via NPE.
 Management switch mac address is learnt on the Agg-NPE router
 Mac table on rest of the PE routers within each L2 service gets updated accordingly.
81
5.5 DSLAM Services
DSLAM consists of 8 Major Services -

1. Management service – This is used for reachability of MSAN or DSLAM device
2. Dynamic service – Used for Internet services, IP is assigned dynamically from a pool
3. Static service – Used for Internet services, static IP is assigned to a customer.
4. Media service – Used for Voice services, so that we can speak with each other.
5. Signaling service – Used for Voice services, dial-tone check.
6. IMS service – It is a combination on media & signaling used for voice service.
7. IPTV service - Internet Protocol television (IPTV) is a system through which
television services are delivered using the Internet protocol suite over a
packet-switched network such as a LAN or the Internet, instead of being
delivered through traditional terrestrial, satellite signal, and cable
television formats.
8. WIFI service - Wi-Fi is a wireless networking technology that uses radio waves to
provide wireless high-speed Internet and network connections.
5.6 DSLAM Configuration Templates
Currently we are using DSLAM service in 13 cites
82
1. NCR
2. Chennai
3. Bangalore
4. Hyderabad
5. Coimbatore
6. Mumbai
7. Pune
8. Ahmedabad
9. Chandigarh &Ludhiana
10. Bhopal
11. Indore
Below are the configuration templates to be used for DSLAM
83

TNG Standard Provisioning Process For CEN

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TNG Standard Provisioning Process For CEN

Hochgeladen von

Copyright:

Verfügbare Formate

TNG Standard Provisioning Process for CEN

Standard Provisioning Process for CEN

3.4 PRI (Primary Rate Interface) .................................................................................... 39

1.3 Scope and Requirements

2.2 CENv2 Network Overview

2.3 Network Topology

From an IP perspective, the existing network topology has a three-tier

Physical Network Topology

protected either by a co-located redundant core router or by a router

Core Network Topology

2.3.2 Aggregator Layer

Aggregation Network Topology

2.3.3 Access Layer

aggregator. In certain deployments dual homed parent aggregator

Access Network Topology

2.3.4 Route Reflector

Route Reflector Topology

No user plane traffic passes through the Route-Reflector, as they

Router Reflector Architecture

CEN diagram with NPE

Coimbatore, Mumbai, Bhopal, Ahmedabad & Pune - Huawei.

In Pune ZTE routers are also being used.

2.5 Provisioning Pre-checks

 Check C1 & C11 values for Bandwidth requirements.

2.6 Bandwidth Utilization Pre-checks

Guidelines for Provisioning

2.7 Provisioning Post-checks

## RA Number - Circuit ID - Customer Name - BW – Date##

 Need to ensure protection path is configured correctly as it may lead to outage if

 For Expressway links (include Multivendor devices) –

 SDP checks to be done in Alcatel devices –

3. CEN Provisioning Services & Configurations

Different services are being deployed in CEN Domain.

3.1 NLD Links (Point to Point on CEN).

3.1.1 Alcatel Router

#Configure service epipe 1274(epipe ID) customer 1 create

service-name "FTTB#CKT ID#B/W#RA number#Date Of Provisioning"

3.1.2 Cisco Router

xconnect 125.62.173.41 100002080 encapsulation mpls

3.1.3 Huawei Router

B end- Primary Aggregator - 10.229.77.57

B end- Secondary Aggregator - 10.229.94.129

3.2 MPLS/ISP/ILP/SDH services (CEN + MPLS/ISP/ILP/SDH link)

Below is the configuration template –

CEN Access Router –

#Configure port 1/5/2

Configure service epipe 1174(epipe ID) customer 1 create

CEN NPE router having NNI with MPLS/ISP/SDH

3.3 Expressway link (Intercity links)

configure service epipe 2457 customer 1 vc-switching create

spoke-sdp 30:2457 create

Note- Same configuration to done from other end.

3.4 PRI (Primary Rate Interface)

The Primary Rate Interface (PRI) is a telecommunications interface standard used

Below is the configuration for same –

group tug3-1 payload vt2

If Last mile is electrical drop (G.703)

sap aps-5.1.1.1.1 (KLM-111) create

spoke-sdp 1434:4869 create

If last mile is Ethernet Drop

configure service epipe 2113 customer 1 create

description "PRI#Customer nameY#OREDER ID#Date Of Provisioning"

A end IP - 10.229.96.188 Port S0/3/0:0