Upload
vuongdang
View
217
Download
2
Embed Size (px)
Citation preview
DEPLOYMENT USE CASES FOR THE ACCESS AND AGGREGATION OF MOBILE NETWORKS September 2012
Pierre Bichon
Sr. Consulting Engineer, EMEA
2 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
AGENDA
I. Requirements review
II. Review of typical use cases for the Mobile Backhaul
III. Seamless MPLS Theory of Operations
IV. Seamless MPLS Reference Model for the Mobile Backhaul
V. Summary
4 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
ACCESS EVOLUTION BUSINESS DRIVERS
Traffic growth and exhaust
of capacity
Service coverage
extension in new areas
Growth objectives or
Competitive pressure
Networkwide or in specific areas ?
Due to a specific subscriber / device segment?
Due to a specific usage e.g. At home, indoor ?
3G Macro
evolution 3G Femto
WiFi
Offload
Digital divide coverage with wireless broadband
New market targets with specific usage
4G
overlay
RAN
renewal
Spectrum
refarm
Leading the innovation (e.g. to capture specific
market share in advance)
Following competitors moves
TCO Control
Market Growth
Customer Retention and Growth
5 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
ACCESS EVOLUTION BUSINESS DRIVERS Bandwidth impact of mobile broadband introduction
Bandwidth patterns impacted by use cases
Combination of Small Cells and non-3GPP access - HetNets
Capacity increase at the cell edge : LTE-A CoMP
Spectrum auctions, refarm; network sharing
Convergence of base stations – RAN refresh
2G/3G/4G base stations
Single VLAN/IP@
Multiple VLANs/IP@
L2 PWs or IP
Access design
Combination of different transport media
Fiber, PDH/SDH, microwave, xPON, xDSL, C/DWDM, etc
Topology diversity (star, ring, mesh)
Impact of X2 in LTE
Impact of CPRI introduction
IMPACTS ON DESIGN
6 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
ACCESS EVOLUTION BUSINESS DRIVERS E2E architecture
Convergence of wireline and wireless driving
architectural change
Transient between initial rollout and full scale
deployment
Cell site / metro functionality in initial and target
architecture (L2 vs.L3)
Wholesale access / metro services
Location of Service Nodes
BSC and RNC
SAE-GW, or S-GW and P-GW
SAMOG GW
Security Gateway
IMPACTS ON DESIGN
7 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
TRENDS SUMMARY FROM SERVICE PROVIDERS AROUND THE WORLD
NEED A UNIFIED TRANSPORT INFRASTRUCTURE END-TO-END
TO ENABLE DIFFERENTIATED SERVICES DELIVERY
-OTT
-VOD
-L3VPN
-VPLS
-IPTV
-WWW
OAM:
-End to end
network, link,
service OAM
-Fault, perf.
mgmt and
reporting
TOPOLOGY /
CONNECTIVITY:
-Ring, Hub-Spoke,
Daisy Chain
-MPLS, ETH, ATM,
TDM
QOS
-service
differentiation
- Mapping
between
layers
FLEXIBILITY:
Re-
configuration,
Network moves
SECURITY:
-Physical,
IPSec, Tunnel,
Encryption
CLOCKING:
-Meet or exceed
circuit network
performance
-Sub-ms accuracy
for LTE Advanced
RESILIENCY:
-interface, port,
transport,
service, link,
network level
CAPEX:
-Fewer and more
powerful network
devices
OPEX:
-Zero touch configuration
& setup
-Low touch maintenance,
automated operations
REVENUES:
-Increased value per bit
(FMC)
-Differentiated services
delivery
UNIVERSAL TRANSPORT
9 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
TOPOLOGICAL DIVERSITY
Case 1: protection and dimensioning are simpler
Case 2: fast detection and restoration needed in aggregation
Case 3&4: increased complexity, suited for MPLS-based solutions
Case Access Aggregation Examples
Case 1 Tree No Aggregation Point-to-point or point-to-multipoint fiber or microwave
connections groomed by a packet node in front of RAN controllers
Case 2 Tree Mesh/Ring Point-to-point or point-to-multipoint fiber or microwave
connections with aggregation by a metro Ethernet or SDH network
Case 3 Ring Mesh/Ring Fiber or microwave based access rings, with metro Ethernet or
SDH aggregation
Case 4 Mesh Mesh/Ring Fiber or microwave based mesh in access, with metro Ethernet or
SDH aggregation
Source: NGMN
10 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
“LTE-READY BACKHAULING SCENARIOS”
Scen. Access Aggregation Protocol stacks
1 Carrier Ethernet Carrier Ethernet Q/Q (S-VLAN, C-VLAN), EoSDH
2 Carrier Ethernet L2/L3 VPN Q/Q + L2 PWs or VPLS
Q/Q + L3 VPN
3 MPLS L2/L3 VPN L2 PW + L2 PW or VPLS
L2 PW + L3 VPN
4 L2/L3 VPN L2/L3 VPN L2 PW or VPLS into VPLS (H-VPLS)
L2 PW or VPLS into L3VPN
L3VPN into L3VPN
5 MS PW MS PW Hierachical PWs
6 “L3” “L3” VPLS E2E or L3VPN E2E
Source: NGMN
11 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
HOW TO “PICK” THE RIGHT SCENARIO
Factors
Installed base, or even the incumbency of previous technical choices
stepwise approach : progressively introduce layer 2 or 3 solutions in the aggregation before considering the transition into the access.
case scenarios 2 or 3 - potentially scenario 1
Greenfield LTE operators or operators wishing to build a converged network also for enterprise and residential services
layer 3 oriented scenarios, e.g. from 4 to 6.
in general, scenario 6 is seen as a target architecture for the medium-long term
Choice based on
technical aspects
organization, skill and attitude, service opportunity, available budget, etc
Source: NGMN
12 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
SOME OBSERVATIONS
Scalability not addressed Number of nodes in the network (routes, MAC@, LSPs etc)
Inter-region / inter-area
Assume domain demarcation at the edge
Migration is key Successful MPLS deployment has been proven
Mainly in L2 mode in the access & aggregation
Dynamic L2 VPN and L3 VPN are simpler (if well designed)
Possible migration steps Introduce Nodes into the OSS, plan OSS automation (P&P etc)
Introduce Aggregation Nodes that are both Q/Q and MPLS capable
Introduce MPLS in the aggregation (and next in pre-aggregation)
Introduce MPLS-capable Access Nodes
Introduce MPLS in the access
13 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
SOME TECHNOLOGIES HAVE CHALLENGES
Q/Q, MPLS-TP, MS-PW have their own challenges
Hierarchy based on provisioning
Domain demarcation at the edge
Additional complexity (provisioning), reliability (OAM) and cost if 2 different technologies in access and aggregation
Introducing MPLS-TP does not bring architectural benefits
Only some additional OAM capabilities
MPLS is a superset of MPLS-TP
Q/Q has been successfully deployed,
Highly driven by CAPEX of Access Nodes
Has challenges : reliability, cost (a lot of provisioning, static behavior)
What is there was a cheap enough MPLS-capable Access Node on the market ?
Do they represent the target architecture ?
14 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
MEF SCENARIOS
IP TNL with L2VPN
a combination of Q/Q, VPLS, H-VPLS, VPWS
IP TNL with L3VPN
L3VPN in access and in aggregation
IP TNL Using L2 & L3
L2 VPN or VPWS or Q/Q in the access, L3VPN in aggregation
16 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
MPLS FUNDAMENTALS
Separation between Control Plane and Data plane
Unified Data plane
De-couple Network and Services
Support for arbitrary Hierarchy
Stack of MPLS labels
Used for multiple Services (aka "virtualization"), Scaling and fast service
Restoration
R1 R2 R3
RX 100K IPv4 routes TX 100K IPv4 routes
inet.0
100K IPv4
FIB entries
R1 R2 R3
RX 100K Labeled routes TX 100K Labeled routes
mpls.0
1 MPLS
FIB entry
17 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
MPLS DECOUPLING SERVICES FROM TRANSPORT
MPLS Data Plane (P2P, P2MP, MP2P, MP2MP)
Ethernet + G.709
DWDM Fiber
PO
TS
, LL,
VC
s
Le
ase
d L
ine
s, F
R
an
d A
TM
PW
s
VoIP
Internet (search, e-
commerce,
advertising,
video, IM,
“over-the-top”
…)
IP-based Infrastructure Control Plane
Eth
ern
et
PW
s
(VP
LS
/VP
WS
)
VoIP
Peering
IP V
PN
s
IPT
V/V
oD
Cab
le T
V D
istr
ibu
tio
n (
via
HF
C
ne
two
rk)
DT
V D
istr
ibutio
n (
Layer
2 o
MP
LS
)
IMS all these
services
delivered
to an IP-
enabled
mobile
handset services
transport
SD
H
IP Services Plane
18 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
FUNCTIONAL BLUEPRINT
Devices and their roles
Access Nodes – terminate local loop from subscribers (e.g. DSLAM, MSAN)
Transport Nodes – packet transport within the region (e.g. Metro LSR, Core LSR)
Border Nodes – enable inter-region packet transport (e.g. ABR, ASBR)
Service Nodes – service delivery points, with flexible topological placement (e.g.BNG, IPVPN PE)
Service Helpers – service enablement or control plane scale points (e.g. Radius, BGP RR)
End Nodes – represent customer network, located outside of service provider network
Regions
A single network divided into regions: multiple Metro regions (leafs) interconnected by WAN backbone (core)
Regions can be of different types: (i) IGP area, (ii) IGP instance, (iii) BGP AS
All spanned by a single MPLS network, with any to any MPLS connectivity blueprints (AN to SN, SN to SN, AN to AN, etc)
Decoupled architectures
Services architecture – defines where & how the services are delivered, incl. interaction between SNs and SHs
Network architecture – provides underlying connectivity for services
Metro-2 Region WAN Backbone Region Metro-1 Region
TN TN BN TN TN BN TN TN AN EN AN EN
SH SH SN SN
Seamless MPLS Network
19 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
FLEXIBLE SERVICE PLACEMENT
End-to-end single MPLS domain, inter-area LSP signaling
Pseudowire access to L2/L3 network services
Flexible topological service placement
Native L3 Services for LTE eNB-eNB connectivity
Access &
Aggregation Backbone
Evolved Transport Network
EN EN
L2/L3
Services
L3 Any-to-Any
Services
LSP PW
LSP AN LSP PW LSP AN
Access &
Aggregation
RNC / BSC
GGSN SGS
N
MME
PGW
SGW
AAA
Multimedia
Database
Server
BRAS &
BNG
SN SN
20 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
SERVICE AND NETWORK ARCHITECTURE
Requirements addressed across the three main architectural dimensions
(1) Scale – enables 100,000s of devices in ONE PSN network
Large network scale via MPLS LSP hierarchy and robust network protocol stack (IGP, BGP)
No service dependency whatsoever – all packet services supported
Low-cost/low-end access devices accommodated natively without adding complexity (MPLS labels on demand)
(2) E2E service restoration – enables sub-50ms recovery from any event
Service restoration made independent of scale, services and failure types
Achieved with full coverage of local-repair mechanisms for sub-50ms restoration
Deterministic for any failure domain size / radius
(3) Pseudowire Headend Termination (PHT) – virtualizing service access
Flexible topological service placement enabled via MPLS PHT
Virtualization of service access with tight integration of Ethernet, IP and MPLS
Minimized number of provisioning points, simplifying service delivery and IT systems
21 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
CPE CPE AGN1 AGN1 AGN2 AGN2
ABR
RR3107
ABR
RR3107 LSR LSR
BGP-LU BGP-LU
ISIS-L1 + LDP-DU ISIS-L2 + LDP-DU ISIS-L1 + LDP-DU Static-Route +
LDP-DoD
Static-Route +
LDP-DoD
NETWORK ARCHITECTURE
RR
BGP-LU
RR
ABR ABR
TN TN AN BN TN TN BN TN TN AN
Seamless MPLS Roles EN EN
push PW-L
push LDP-L
PW-L
swap BGP-L
push LDP-L
PW-L
BGP-L
swap LDP-L
PW-L
BGP-L
swap LDP-L
PW-L
BGP-L
swap LDP-L
PW-L
BGP-L
pop LDP-L
PW-L
swap BGP-L
push LDP-L
PW-L
BGP-L
pop LDP-L
PW-L
pop BGP-L
pop PW-L
Data flow
Network
Control
Plane
Data
Plane
Service
Control
Plane
Targeted LDP
MPLS data plane
Pseudowire
NHS no NHS NHS no NHS
LDP DoD – LDP Downstream on Demand, RFC5036
LDP DU – LDP Downstream Unsolicited, RFC5036
BGP LU – BGP Label Unicast, RFC3107
NHS – BGP next-hop-self
22 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
NETWORK SCALE
Design
Split the network into regions: access, metro/aggregation, edge, core
Single IGP with areas per metro/edge and core regions
Hierarchical LSPs to enable e2e LSP signaling across all regions
IGP + LDP for intra-domain transport LSP signaling RSVP-TE as alternative
BGP labeled unicast for cross-domain hierarchical LSP signaling
LDP Downstream-on-Demand for LSP signaling to/from access devices
Static routing on access devices
IGP as alternative
Properties
Large scale achieved with hierarchical design
BGP labeled unicast enables any-to-any connectivity between >100k devices – no service dependencies (e.g. no need for PW stitching for base VPWS service)
A simple MPLS stack on access devices (static routes or IGP, LDP DoD)
BGP VPNs still possible
23 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
SCALE ENABLERS - LDP DOWNSTREAM-ON-DEMAND (LDP DOD)
IP/MPLS routers implement LDP Downstream Unsolicited (LDP
DU) label distribution
Advertising MPLS labels for all routes in their RIB
This is very insufficient for Access Nodes
Mostly stub nodes, can rely on static routing and need reachability to a
small subset of total routes (labels)
AN requirement for scale and simplicity is addressed with LDP
DoD
LDP DoD (RFC5036 ) enables on-request label distribution
ensuring that only required labels are requested, provided and
installed
24 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
AGN1b AGN2a
LDP DoD
SCALE ENABLERS - LDP DOD CONFIGURATION AND OPERATION
AGN1b AGN2b
IP/MPLS
Backbone
LDP DU
iBGP LU
Static routes:
0/0 default
/32 destination
Static route:
/32 AN loopback
IGP (ISIS,OSPF)
DSLAM
OLT
DSLAM
OLT
IP/MPLS Network
ABRa
ABRb
IGP
LDP DU
3
1
2
4
5
7
8 6
(*) Requires LDP support for longest match prefix in RIB (in addition to the exact match) as per RFC5283.
LDP DoD – Label Distribution Protocol, Downstream on Demand distribution, RFC5036
LDP DU – Label Distribution Protocol, Downstream Unsolicited distribution, RFC5036
BGP LU – Border Gateway Protocol, Label Unicast extensions, RFC3107
① AN: provisioned static routes
② AGN1: provisioned static routes
③ AGN1: statics redistributed into IGP (optional)
④ AGN1: statics redistributed into BGP-LU
⑤ AN: LDP DoD lbl mapping requests for FECs associated
with /32 static routes and configured services using /32
routes matching default route(*)
⑥ AGN1: LDP DoD lbl mapping requests for static route /32
FECs
⑦ AGN1: AN loopbacks advertised in iBGP LU
⑧ AGN1: if (3) AN loopbacks advertised in LDP DU
25 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
SCALE ENABLERS BGP LABELED UNICAST (RFC3107)
BGP-LU enables distribution of /32 router loopback MPLS FECs
Used between Seamless MPLS regions for any2any MPLS reachability
Enables large scale MPLS network with hierarchical LSPs
Not all MPLS FECs have to be installed in the data plane
Separation of BGP-LU control plane and LFIB
Only required MPLS FECs are placed in LFIB
E.g. on RR BGP-LU FECs with next-hop-self
E.g. FECs requested by LDP-DoD by upstream
Enables scalability with minimum impact on data plane resources – use
what you need approach
26 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
E2E SERVICE RESTORATION - Local vs. Global Repair
link break, local-repair start
local repair stop global repair stop
20 - 50ms 200 – 1000+ ms
Local-repair complements Global-repair
Local-repair keeps traffic flowing while
Global-repair gets things right
Variation of “Make before break”
global repair start
Local-repair
Based on the pre-computed local backup
forwarding state - provides sub-50msec
restoration
Global-repair
Requires signaling to take place after failure
detection - can provide sub-1sec or longer
restoration times
27 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
E2E SERVICE RESTORATION
Design
IPFRR/LFA for local-repair of transit MPLS link and node failures
TE FRR as alternative to LFA
LSP tail-end protection for egress PE node failures (IP, L3VPN, L2VPN, BGP-LU, RR-NHS)
Optimized global-repair as fall-back if local-repair not feasible (e.g. no LFA cover)
Note: LFA cover can be extended with RSVP-TE
BGP PE-CE link local-repair protection for BGP edge link failures (IP, L3VPN, L2VPN, BGP3107)
Properties
Local-repair for all PE access links, PE and P nodes
Local-repair for all PE/P transit links, topology independent (albeit certain topologies may introduce
increased complexity e.g. RSVP-TE if no LFA coverage)
E2E restoration in O(50ms) achievable, regardless of network and service scale
28 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
E2E SERVICE RESTORATION - IP/MPLS LOCAL-REPAIR COVERAGE
Ingress: CE-PE link, PE node failure
ECMP, LFA
Transit: PE-P, P-P link, P node failure
LFA based on IGP/LDP; if no 100% LFA coverage, delta with RSVP-TE
RSVP-TE FRR
Egress: PE-CE link failure BGP PE-CE link local protection
Egress: PE node failure LSP tail-end protection with context label
lookup on the backup PE
Failure repaired locally by adjacent P router using LFA (or TE-FRR)
Packet based networks can provide E2E service protection similar to SDH 1:1 protection, regardless of network size and service scale
This provides network layer failure transparency to service layers, becoming a major enabler for network consolidation
(*) “High Availability for 2547 VPN Service”, Y.Rekhter, MPLS&Ethernet World Congress, Paris 2011.
29 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
MPLS AND ETHERNET OAM COVERAGE
Technologies
Fa
ult
Dete
cti
on
Fa
ult
Ve
rifi
ca
tio
n
Fa
ult
Lo
ca
liza
tio
n
Fa
ult
No
tifi
ca
tio
n
Pe
rfo
rma
nc
e
Lo
ss
Rati
o
Pe
rfo
rma
nc
e
Fw
d D
ela
y
Pe
rfo
rma
nc
e
Fw
d D
ela
y
Va
ria
tio
n
Eth
ern
et
802.3ah Yes Yes Remote LB (Critical) Link Events Remote
Fault Indication No No No
E-LMI N/A N/A N/A Yes N/A N/A N/A
802.1ag CC LB LT RDI No No No
Y.1731 CC LB LT RDI, AIS ETH-LM ETH-DM ETH-DM
IP/M
PL
S
LSP LSP-BFD LSP-Ping LSP-Ping/TR LDP, RSVP RPM RPM RPM
PWE3 VCCV-BFD VCCV-Ping VCCV-Ping/TR BGP, tLDP, VCCV-BFD RPM RPM RPM
L2VPN BGP, VCCV-BFD BGP, VCCV-Ping BGP, VCCV-Ping/TR BGP RPM RPM RPM
IPVPN BFD, IGP, MP-
BGP Ping TR IGP, MP-BGP RPM RPM RPM
Comprehensive OAM implementation across IP/MPLS and Ethernet
Simplified end-to-end troubleshooting and performance monitoring
31 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
MOBILE BACKHAUL – REFERENCE MODEL(1)
Edge Region - 1 Edge Region - 2 Transport Region
PE1 P1 ASBR1 ASBR2 P2 ASBR3 ASBR4 P3 PE2
Local IGP
Local Transport LSP
Local IGP
Local Transport LSP Local IGP
Local Transport LSP
Inter-Region Transport LSP Inter-Region Transport LSP Inter-Region Transport LSP
Inter-Region Service Plane
- Multiple Autonomous Systems
32 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
Edge Region - 1 Edge Region - 2 Transport Region
PE1 P1 ABR1 P2 ABR2 P3 PE2
Local IGP
Local Transport LSP
Local IGP
Local Transport LSP Local IGP
Local Transport LSP
Inter-Region Transport LSP Inter-Region Transport LSP Inter-Region Transport LSP
Inter-Region Service Plane
- Single Autonomous System – Multiple Areas/Levels
MOBILE BACKHAUL – REFERENCE MODEL(2)
33 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
ISIS level 1 with BFD ISIS level 2 with BFD Physically connected ISIS level 2 with BFD
AS 65001 AS 65002
RSVP with BFD RSVP with BFD Physically connected RSVP with BFD
3107 E-BGP with BFD 3107 I-BGP with BFD 3107 I-BGP with BFD LDP DoD over RSVP
Any Service
Any Service
Any Service
Any Service
Any Service
SEAMLESS MPLS ARCHITECTURE
33
1588v2 GM CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Core
34 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
ISIS level 1 with BFD ISIS level 2 with BFD Physically connected ISIS level 2 with BFD
AS 65001 AS 65002
RSVP with BFD RSVP with BFD Physically connected RSVP with BFD
3107 E-BGP with BFD 3107 I-BGP with BFD 3107 I-BGP with BFD LDP DoD over RSVP
Any Service
Any Service
Any Service
Any Service
Any Service
SEAMLESS MPLS ARCHITECTURE
34
1588v2 GM CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Core
35 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
SEAMLESS MPLS ARCHITECTURE SOLUTION OPTIONS
1) End to End L3 MPLS VPN
2) Pseudo wire in Access & L3 MPLS VPN in Agg/Core
3) Pseudo wire in Access & VPLS in Agg/Core
4) TDM/ATM PWs
36 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
ISIS level 1 with BFD ISIS level 2 with BFD Physically connected ISIS level 2 with BFD
AS 65001 AS 65002
RSVP with BFD RSVP with BFD Physically connected RSVP with BFD
3107 E-BGP with BFD 3107 I-BGP with BFD 3107 I-BGP with BFD
MP-EBGP (VPNv4) MP-IBGP (VPNv4)
All VPNv4 prefixes All VPNv4 prefixes
Aggregate/default route only Aggregate/default route only
1) L3VPN END-TO-END TOPOLOGY
36
1588v2 GM L3VPN Instance with vrf-table-label. All CSRs and Pre-Agg routers have the L3VPN instance
All RSVP will have primary and secondary paths with fast reroute
Agg routers are RRs for Pre-aggs Pre-agg routers are RRs for CSRs
CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Core
37 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
1) L3VPN END-TO-END TOPOLOGY IGP DESIGN - ACCESS
1588v2 GM L3VPN Instance with vrf-table-label. All CSRs and Pre-Agg routers have the L3VPN instance
All RSVP will have primary and secondary paths with fast reroute
Agg routers are RRs for Pre-aggs Pre-agg routers are RRs for CSRs
CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Core
Level-1 ISIS area.
BFD at 10ms for ISIS fast convergence.
5 to 7 routers in a ring. (typically example)
Each pair of AG1 routers can terminate
multiple rings.
- 30 nodes to 200 nodes per Pre-Agg pair.
Each ISIS area with up to 200 routers.
No route-leaking, unless specific reasons,
between Access and Pre-Agg rings.
38 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
1) L3VPN END-TO-END TOPOLOGY LSP DESIGN - ACCESS
38
1588v2 GM L3VPN Instance with vrf-table-label. All CSRs and Pre-Agg routers have the L3VPN instance
All RSVP will have primary and secondary paths with fast reroute
Agg routers are RRs for Pre-aggs Pre-agg routers are RRs for CSRs
CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Core
RSVP based LSPs from each CSR.
LSPs from CSR to a pair of AG1s
[Pre-Agg Nodes].
FRR/LP/NLP based protection.
Secondary LSP paths if needed.
Full mesh of LSPs if needed.
39 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
1) L3VPN END-TO-END TOPOLOGY IGP DESIGN - AGGREGATION
39
1588v2 GM L3VPN Instance with vrf-table-label. All CSRs and Pre-Agg routers have the L3VPN instance
All RSVP will have primary and secondary paths with fast reroute
Agg routers are RRs for Pre-aggs Pre-agg routers are RRs for CSRs
CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Core
Level-2 ISIS area.
BFD at 10ms for ISIS fast convergence.
Each pair of AG2 routers can terminate
multiple rings.
No route-leaking between Access and Pre-Agg rings.
40 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
1) L3VPN END-TO-END TOPOLOGY LSP DESIGN - AGGREGATION
40
1588v2 GM L3VPN Instance with vrf-table-label. All CSRs and Pre-Agg routers have the L3VPN instance
All RSVP will have primary and secondary paths with fast reroute
Agg routers are RRs for Pre-aggs Pre-agg routers are RRs for CSRs
CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Core
RSVP based LSPs.
LSPs from AG1s and AG2 pair.
FRR/LP/NLP based protection.
Secondary LSP paths if needed.
41 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
ISIS level 1 with BFD ISIS level 2 with BFD Physically connected ISIS level 2 with BFD
AS 65001 AS 65002
RSVP with BFD RSVP with BFD Physically connected RSVP with BFD
1) L3VPN END-TO-END TOPOLOGY IGP AND LSP SUMMARY
41
1588v2 GM L3VPN Instance with vrf-table-label. All CSRs and Pre-Agg routers have the L3VPN instance
All RSVP will have primary and secondary paths with fast reroute
Agg routers are RRs for Pre-aggs Pre-agg routers are RRs for CSRs
CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Core
42 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
3107 E-BGP with BFD 3107 I-BGP with BFD 3107 I-BGP with BFD
MP-EBGP (VPNv4) MP-IBGP (VPNv4)
All VPNv4 prefixes All VPNv4 prefixes
Aggregate/default route only Aggregate/default route only
1) L3VPN END-TO-END TOPOLOGY BGP DESIGN SUMMARY
42
1588v2 GM L3VPN Instance with vrf-table-label. All CSRs and Pre-Agg routers have the L3VPN instance
All RSVP will have primary and secondary paths with fast reroute
Agg routers are RRs for Pre-aggs Pre-agg routers are RRs for CSRs
CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Core
43 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
ISIS level 1 with BFD ISIS level 2 with BFD Physically connected ISIS level 2 with BFD
AS 65001 AS 65002
RSVP with BFD RSVP with BFD Physically connected RSVP with BFD
3107 E-BGP with BFD 3107 I-BGP with BFD 3107 I-BGP with BFD
MP-EBGP (VPNv4) MP-IBGP (VPNv4)
All VPNv4 prefixes All VPNv4 prefixes
Aggregate/default route only Aggregate/default route only
1) L3VPN END-TO-END TOPOLOGY TRAFFIC FLOW FROM CSR TO EPC (A->B)
43
1588v2 GM L3VPN Instance with vrf-table-label. All CSRs and Pre-Agg routers have the L3VPN instance
All RSVP will have primary and secondary paths with fast reroute
Agg routers are RRs for Pre-aggs Pre-agg routers are RRs for CSRs
CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Core
A B BGP-L : 1111
VC-L : 4444 VC-L : 99
vrf ip look up push 99,10
swap 10->20
pop 20
push 4444,2222,100
swap 100->200 pop 200
swap 2222->1111 pop 1111
44 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
ISIS level 1 with BFD ISIS level 2 with BFD Physically connected ISIS level 2 with BFD
AS 65001 AS 65002
RSVP with BFD RSVP with BFD Physically connected RSVP with BFD
3107 E-BGP with BFD 3107 I-BGP with BFD 3107 I-BGP with BFD
MP-EBGP (VPNv4) MP-IBGP (VPNv4)
All VPNv4 prefixes All VPNv4 prefixes
Aggregate/default route only Aggregate/default route only
1) L3VPN END-TO-END TOPOLOGY TRAFFIC FLOW FROM CSR TO EPC (B->A)
44
1588v2 GM L3VPN Instance with vrf-table-label. All CSRs and Pre-Agg routers have the L3VPN instance
All RSVP will have primary and secondary paths with fast reroute
Agg routers are RRs for Pre-aggs Pre-agg routers are RRs for CSRs
CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Core
A B BGP-L : 3333
BGP-L : 5555
BGP-L : 7777
VC-L : 88 VC-L : 8888
vrf ip look up push 88,100
swap 100->200 pop 200
swap 5555->100 swap 7777->5555
push 8888,7777 swap 100->200
pop 200
45 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
ISIS level 1 with BFD ISIS level 2 with BFD Physically connected ISIS level 2 with BFD
AS 65001 AS 65002
RSVP with BFD RSVP with BFD Physically connected RSVP with BFD
3107 E-BGP with BFD 3107 I-BGP with BFD 3107 I-BGP with BFD
MP-EBGP (VPNv4) MP-IBGP (VPNv4)
All VPNv4 prefixes All VPNv4 prefixes
Aggregate/default route only Aggregate/default route only
1) L3VPN END-TO-END TOPOLOGY END-TO-END TRAFFIC FLOW
45
1588v2 GM L3VPN Instance with vrf-table-label. All CSRs and Pre-Agg routers have the L3VPN instance
All RSVP will have primary and secondary paths with fast reroute
Agg routers are RRs for Pre-aggs Pre-agg routers are RRs for CSRs
CSR
Access
Pre-Agg
Agg
Service Node
Core
A B X2
S1
46 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
ISIS level 1 with BFD ISIS level 2 with BFD Physically connected ISIS level 2 with BFD
AS 65001 AS 65002
RSVP with BFD RSVP with BFD Physically connected RSVP with BFD
3107 E-BGP with BFD 3107 I-BGP with BFD 3107 I-BGP with BFD
MP-EBGP (VPNv4) MP-IBGP (VPNv4)
All VPNv4 prefixes All VPNv4 prefixes
Aggregate/default route only Aggregate/default route only
1) L3VPN END-TO-END TOPOLOGY TRAFFIC FLOW IN THE ACCESS
46
1588v2 GM L3VPN Instance with vrf-table-label. All CSRs and Pre-Agg routers have the L3VPN instance
All RSVP will have primary and secondary paths with fast reroute
Agg routers are RRs for Pre-aggs Pre-agg routers are RRs for CSRs
CSR
Access
Pre-Agg
Agg
Service Node
Core
A B X2
S1
X2
S1:
Several VRFs may be used (S1-U, S1-MME)
Applies also to S1-Flex
Dedicated VRFs:
Other VRFs can be provisioned for Management, billing,
wholesale, Business VPNs, etc
X2:
In the X2 case, any to any can be achieved:
RSVP full mesh (auto-mesh)
iBGP full mesh
Or any partial mesh
At the expense of additional provisioning
X2 over 2 access rings still go through the pre-Aggregation
node
47 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
2) L2CKT + L3VPN TOPOLOGY
ISIS level 1 with BFD ISIS level 2 with BFD Physically connected ISIS level 2 with BFD
AS 65001 AS 65002
RSVP with BFD RSVP with BFD Physically connected RSVP with BFD
3107 E-BGP with BFD 3107 I-BGP with BFD 3107 I-BGP with BFD
MP-EBGP (VPNv4)
L2Ckt with PW redundancy
All VPNv4 prefixes
Aggregate/default route only Stub Network
1588v2 GM CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
L3VPN Instance with vrf-table-label. All Pre-Agg routers have the L3VPN instance. L2CKT terminates into L3VPN using LT interfaces. All RSVP will have primary and secondary paths with fast reroute Agg routers are RRs for Pre-aggs Phase 1: L2Ckt is in backup mode (non-hot standby) Phase 2: L2Ckt is in hot-standby redundancy mode using Status TLV
L2ckt. All CSRs will originate L2ckts
Core
48 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
3) L2CKT-VPLS END-TO-END TOPOLOGY
ISIS level 1 with BFD ISIS level 2 with BFD Physically connected ISIS level 2 with BFD
AS 65001 AS 65002
RSVP with BFD RSVP with BFD Physically connected RSVP with BFD
3107 E-BGP with BFD 3107 I-BGP with BFD 3107 I-BGP with BFD
VPLS L2Ckt with PW redundancy
1588v2 GM CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
VPLS Instance . All Pre-Agg routers have the VPLS instance. L2CKT terminates into VPLS using virtual switch.
All RSVP will have primary and secondary paths with fast reroute Agg routers are RRs for Pre-aggs
L2ckt. All CSRs will originate L2ckts
Phase 1: L2Ckt is in backup mode (non-hot standby) Phase 2: L2Ckt is in hot-standby redundancy mode using Status TLV
Core
49 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
4) TDM AND ATM – SINGLE HOMED
ISIS level 1 with BFD ISIS level 2 with BFD Physically connected ISIS level 2 with BFD
AS 65001 AS 65002
RSVP with BFD RSVP with BFD Physically connected RSVP with BFD
3107 E-BGP with BFD 3107 I-BGP with BFD 3107 I-BGP with BFD LDP DoD over RSVP
SATOP, CESOP and ATM PWs with PW redundancy (Intra/Inter Chassis APS)
The above topology is not typical for TDM/ATM termination in MBH. They are usually terminated on or closer to Agg-routers. In
that case, the design would be much simpler, but would still fall under the same boarder Seamless-MPLS design.
1588v2 GM CSR
Access Pre-Aggregation
Pre-Agg
Agg
Core
Service Node
Service end points
ATM : IMA on CSR and STM-1 or GE on Service Node TDM: SATOP or CESOP
50 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
4) TDM AND ATM – DUAL HOMED
ISIS level 1 with BFD ISIS level 2 with BFD
AS 65001
RSVP with BFD RSVP with BFD
3107 I-BGP with BFD LDP DoD over RSVP
SATOP, CESOP and ATM PWs with PW redundancy (Intra/Inter Chassis APS)
The above topology is not typical for TDM/ATM termination in MBH. They are usually terminated on or closer to Agg-routers. In
that case, the design would be much simpler, and would still fall under the same boarder Seamless-MPLS design.
1588v2 GM CSR
Access Pre-Aggregation
Pre-Agg
Agg
Service Node
Service end points
ATM : IMA on CSR and STM-1 or GE on Service Node TDM: SATOP or CESOP
52 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
Assessment
Criteria Value Proposition
Service Decoupling ✓ Services decoupled from Network Architecture, changes in one do not affect the other –
prime foundation for robust converged one PSN
New Services Rollout ✓ Simple, no re-design, no complex interop, faster Time-To-Market, incremental platform
evaluation and deployment
Operations Simplicity ✓ Operational procedures re-usability, flexibility and lower complexity (no customer state in
aggregation nodes)
Ubiquitous Service
Availability ✓ E2E service restoration completely transparent to service layer for all failures and services
(conceptually similar to SDH model – it worked!)
Address Diverse
Customer Density ✓ Optimal topological service placement based on service, network and operational economics
Scale ✓ Higher scale at lower cost due to customer and service transparency in access, aggregation
and core
TCO ✓ Optimized CAPEX with simpler access/aggregation/edge, simpler E2E operations for lower
OPEX
SEAMLESS MPLS ARCHITECTURE VALUE PROPOSITION
53 Copyright © 2012 Juniper Networks, Inc. www.juniper.net
SUMMARY
Seamless MPLS, along with an efficient end-to-end implementation in hardware and software, creates a new dimension in the architecture and economics of the mobile infrastructure
Other topics not addressed here, though relevant and that the model can integrate:
QoS
Security
Policy & Control
Network timing
Intelligent integration of microwave technology
Network Monitoring
OSS, part of which are:
Automation (SON)
Static and dynamic provisioning (static and dynamic MPLS-TP)
FMC aspects: residential access, business access, multicast etc