LTRMPL 3843

LTRMPL-3843
Design, Deployment and

Troubleshooting Scalable
MPLS Architecture (Platform
: IOS-XR, IOS-XE)
Vinit Jain, Technical Leader Services CCIE # 22854

Twitter @vinugenie
Shashi Shekhar Sharma, Customer Advocacy Engineer
Twitter @Shekhar1988
Cisco Spark
Questions?
Use Cisco Spark to communicate
with the speaker after the session
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
cs.co/ciscolivebot#LTRMPL-3843
© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
Agenda
• Introduction
• Seamless MPLS Overview
• Deployment Models
• Design Breakdown
• Lab Overview and Packet Flow
• Control and Forwarding Plane flow
• Accessing the Lab
• Lab it 
Session Goal
• Introduction of Scalable MPLS Architecture
• Hands-on LAB (Scalable MPLS)
• Migration Strategy
• CASE STUDY (In design aspect)
This hands-on lab and we will be cover details packet flow during this session will provide
students with an opportunity to configure Scalable MPLS Deployment Models, and analyze
the functionality using Cisco IOS and XR configuration, show commands and debugs
This session also provides CASE STUDY on Scalable and its Design Aspects
Students MUST have a basic understanding of MPLS
Students MUST have familiarity with Cisco IOS and its CLI
LTRMPL-3843 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 5
Session Coverage
• Focus is to understand how the Seamless MPLS network is built and how to
make the network more scalable
• Primary focus on integration of BGP 3107, LDP, RSVP and deployment of L2
and L3 VPNs
• All lab routers are IOS, XE and XR based
GOALS
• Selection of different signaling protocols, features and configuration options affects the
amount of state created, and what are the tradeoffs involved.
• Analyze few common mistakes when doing scalability analysis.
• Techniques available for improving scaling in MPLS deployments.
Why Scalable MPLS ?
GOALS FOR SEAMLESS MPLS
IP traffic increases rapidly due to video, cloud, mobile internet, multimedia
services and so on. To cope with the growth rate of IP Traffic, we increase our
networks capacity but at the same time we have to maintain operational simplicity.
Very large scale: from < 1000 nodes today to 10 to 100 thousand nodes in a
single MPLS network
All-encompassing: access, metro, core
Robust: protocols, devices, OAM
Resilient: 50 msec service restoration
Service flexibility
• The network architecture to achieve the above requirements must not constrain
services in any way
Network end-to-end Scalability and Resilience with MPLS
MPLS in Access/Edge for benefits like better Scalability, TE, QOS and resiliency
Advantages:
1. Offloads the core since many routing decisions can be made in the access.
2. Enables fast service creation/delivery that supports legacy and future services.
3. Optimizes bandwidth utilization throughout the network
4. Scale the network beyond VLAN limitation to practically unlimited
5. Ensures service delivery during Moves/Adds/Changes in the network
6. Eases management and maintenance by using a single technology end-to-end
7. Increase number of classes of Service using Hierarchical Qos
8. Supports OAM at various layers to prevent unnecessary truck rolls.
Seamless MPLS Overview
Seamless MPLS is the umbrella portfolio that provides the framework for taking MPLS to
the access in a scalable fashion, extending the benefits of TE and LFA / RLFA and
guaranteed service level agreements (SLAs) with deterministic network resiliency.
Building Multi-Generation Scalable Networks with End-to-End MPLS.
Service Flexibility and Simplified Provisioning:
key benefits and requirements with taking MPLS to the access and building seamless MPLS
networks:
1. Service flexibility and simplified provisioning and operations
2. Network resiliency with deterministic, sub-second, end-to-end convergence for services
3. Scale to the order of 100,000 nodes network-wide without compromising any of the
benefits
IMPLEMENTATION: SEAMLESS MPLS
Network Scale and End-to-End service restoration
• MPLS in the access, 100,000s of devices in ONE packet network
• Seamless service recovery from any failure event (Sub-50ms)
Decoupled network and service architectures
• Complete virtualization of network services
• Flexible topological placement of services – enabler for per service de-centralization
• Minimized number of provisioning points, simplified end-to-end operation
Building Seamless MPLS Networks
• Service flexibility, simplified provisioning, simplified operations Seamless MPLS
architecture is a systematic way of enabling MPLS end-to-end.
• Clean separation of control plane, management plane, and data plane
operations throughout the network.
• Optimized and simplified service provisioning and operations, making it possible
to minimize the number of service provisioning points.
• Network resiliency with deterministic, subsecond, end-to-end convergence for
services MPLS has significant traffic engineering capabilities, enabling end-to-
end service restoration.
• Scale to the order of 100,000 nodes network-wide without compromising any of
the benefits Seamless MPLS enhances the capacity to scale as needed.
DECOUPLING ARCHITECTURES
• Ultimately, a Service Provider needs to provide services (even if it is just basic
connectivity)
• Service architecture defines where and how a service is delivered, and the
interaction of service nodes and service helpers to enable the service
• Network architecture provides the underlying connectivity functions (QoS, CAC,
FRR, …) to make each service as effective as possible
• These architectures need to be as decoupled and independently managed as
feasible
Agenda
• Introduction
• Seamless MPLS Overview
• Deployment Models
• Design Breakdown
• Lab Overview and Packet Flow
• Accessing the Lab
• Lab it 
Unified MPLS Architecture Models
• Architecture Models based on
• Access Type – Ethernet/TDM Access or MPLS Access
• Network Size – Small/Med or Large Networks
• Small Network:
• 1. Ethernet and TDM Access: Flat LDP Core and Aggregation
• 2. MPLS Access: Hierarchical Labeled BGP Access Network
• Large Network:
• Ethernet/TDM Access:
• 3. Hierarchical Labeled BGP Core and Aggregation Network
• Large Network :
• 4. Hierarchical Labeled BGP Access, Aggregation and Core Network
• 5. Labeled BGP Redistribution into Access Network IGP/LDP
• Architecture Models based on:
• Access Type: Ethernet TDM or MPLS access
• Network Size: Small/Medium (1000 nodes or less) or Large
• End to Labeled Switch Path
Deployment Network Size Access Type Core/Aggregation LSP

Model
1 Small/Medium Ethernet/TDM Flat LDP
2 Small/Medium MPLS Hierarchical Labeled BGP
3 Large Ethernet Hierarchical Labeled BGP
4 Large MPLS Hierarchical Labeled BGP for Core,
Aggregation and Access
Aggregation with redistribution in
Access
1 – Small Network: Ethernet/TDM Access
Flat LDP LSP across Core and Aggregation Networks
Mobile
Core Node Transport GW Core Node
Aggregation Node Aggregation Node CSG
IP/Ethernet
Aggregation Core and Aggregation Pre-Aggregation
Node Node Business
Distributio IP/MPLS Domain
n Node
Aggregation Node Mobile Aggregation Node
TDM and Packet Fiber and Microwave
Microwave, 2G/3G/LTE 3G/LTE
IGP/LDP domain
• Core and Aggregation Networks form one IGP and LDP domain.
• Scale recommendation is less than 1000 IGP/LDP nodes
• Packet Microwave links aggregated in Aggregation Nodes
• Mobile Access is based on TDM
• All services –Mobile and Wireline– enabled by Aggregation Nodes
2 – Small Network: MPLS Access
Hierarchical BGP LSP Across Core + Aggregation and Access Networks
Aggregation Node Aggregation Node
Core Node Mobile Core Node
Transport GW CSG
CSG
RAN
RAN
Core and Aggregation IP/MPLS Domain
IP/MPLS Domain Pre-Aggregation Pre-Aggregation
Node IP/MPLS domain Node CSG
CSG IGP Area
Mobile
Transport GW
Core Node Core Node CSG
CSG Aggregation Node
Aggregation Node
iBGP Hierarchical LSP
LDP LSP LDP LSP LDP LSP
• The Core and Aggregation form a relatively small IGP/LDP domain (1000 nodes)
• MPLS enabled RAN, each RAN forms a different IGP/LDP domain
• The Core/Aggregation and RAN Access Networks are integrated with labelled BGP LSP
• The Access Network Nodes learn only the MPC labelled BGP prefixes and selectively and
optionally the neighbouring RAN networks labelled BGP prefixes.
3 – Large Network: Ethernet/TDM access
Hierarchical BGP LSP Across Core Network and Aggregation Networks
Aggregation Node
Aggregation Node
Mobile
Transport GW CSG
Core Core
Aggregation Network Node Node Aggregation Network IP/Ethernet
IP/MPLS Core Network IP/MPLS
Domain IP/MPLS Domain Domain
Core CSG
Aggregation Core Pre-Aggregation
Node Node Mobile Node Node
Transport GW
Aggregation Node
TDM and Packet Aggregation Node Fiber and Microwave
Microwave, 2G/3G/LTE 3G/LTE
iBGP (eBGP across ASes) Hierarchical LSP
• Core and Aggregation Networks enable Unified MPLS Transport

• Core and Aggregation Networks are organized as independent IGP/LDP domains
• Core and Aggregation Networks may be in same or different Autonomous Systemss
• The network domains are interconnected with hierarchical LSPs based on RFC 3107, BGP IPv4+labels
• No MPLS in Access Domian
• Aggregation Node enable Mobile and Wireline Services over Unified MPLS transport.
4 – Large Network: MPLS Access
Hierarchical BGP LSP Across Core, Aggregation and Access Networks
Aggregation Node
Aggregation Node
Mobile
Transport GW Core Node CSG
CSG Core Node
Core Core
Aggregation Network Node Aggregation Network RAN
RAN Node
Core Network IP/MPLS
IP/MPLS IP/MPLS IP/MPLS domain
domain Domain IP/MPLS Domain Domain
Pre-Aggregation CSG
CSG Core Core Pre-Aggregation
Node Node Mobile Node Node
CSG
Aggregation Node
iBGP (eBGP across ASes) Hierarchical LSP
LDP LSP LDP LSP LDP LSP LDP LSP LDP LSP
• Core, Aggregation, Access Network enable Unified MPLS Transport

• Core, Aggregation, Access are organized as independent IGP/LDP domains
• Core and Aggregation Networks may be in same or different Autonomous Systems
• Network domains are interconnected with hierarchical LSPs based on RFC 3107, BGP IPv4+labels.
• Intra domain connectivity is based on LDP LSPs
• The Access Network Nodes learn only the required labelled BGP FECs
5 - Large Network, MPLS Access
Hierarchical BGP LSP with IGP/LDP Redistribution in Access Network
Aggregation Node
Aggregation Node
Mobile
MPC iBGP community Transport GW Core
Core
Node MPC iBGP community CSG
CSG Core
Core
Node
Core
into RAN IGP Aggregation Network
Core into RAN IGP
RAN Node Node Aggregation Network
RAN
MPLS/IP IP/MPLS Core Network IP/MPLS MPLS/IP
Domain IP/MPLS Domain Domain
IGP Area/Process Pre-Aggregation Pre-Aggregation IGP Area/ProcessCSG
CSG Core Core Node
Node
Node Core Mobile Node
RAN IGP CSN Loopbacks Core
Core
Node RAN IGP CSN Loopbacks
Core Node Transport GW
into iBGP into iBGP
CSG
Aggregation Node
i/eBGP Hierarchical LSP
LDP LSP LDP LSP
• Core and Aggregation are distinct IGP/LDP domains that enable inter domain hierarchical LSPs
• Core and Aggregation Networks may be in same of different Autonomous Systems
• Redistribution of Core/Aggregation LSPs into Access Networks IGP
Summary and Applicability
• Multiple deployment models to fit different architectures
• Support for End to End Unified MPLS with Labeled BGP
• Support for non-Unified MPLS Access Domains
Deployment Network Size Access Type Core/Aggregation LSP
Model
1 Small/Medium Ethernet/TDM Flat LDP
2 Small/Medium MPLS Hierarchical Labeled BGP
3 Large Ethernet Hierarchical Labeled BGP
Aggregation and Access
Aggregation with redistribution in Access
Key Technologies used with Seamless MPLS Design
• Label Downstream on Demand
• For scalable labe distribution between DSLAM and AGS2
• ISIS LFA (Loop Free Alternate)
• Scalable and simple to use protection mecanism for all non BGP related network
failures (sub 50ms)
• BGP PIC edge (Prefix Independant Convergence)
• Scalable and simple to use protection mecanism for BGP endpoint failure protection
(200-500ms)
• BGP anycast / BGP node mirroring
• Mirroring label assignment between ABR routers and fall back on local protection with
LFA for all failures (sub 50ms)
• BGP next-hop-self on RR / BGP add-path
Lets Break It Down 
Reference Topology
ISIS L2
ISIS L1 ISIS L1
L1 L2 L2 L1
AGS1 A1 AGS2 A1 ABR A1 LSR A1 LSR A2 ABR A2 AGS2 A2 AGS1 A2
L1 L1/L2 L2 L2 L1/L2 L1
DSLAM 1
DSLAM 2
AGS1 B1 AGS2 B1 L1 ABR B1 L2 LSR B1 LSR B2 L2 ABR B2 L1 AGS2 B2 AGS1 B2
1.000 Nodes / Core
10.000 Nodes / Aggregation
100.000 Nodes / Access
LTRMPL-3843 © 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public
AGS1 AGS1A 16x10GE
1 16 AGS2 BRAS
A1
AGS1 AGS1B 16x10GE

DSLAM AGS2
1 16
1 - 200 B1
L1 area1
AGS1 AGS1 16x10GE
1 16 AGS2
A1
ABR A1
AGS1 AGS1 16x10GE
1 16 AGS2
DSLAM B1
1 - 200
LSR A
AGS1 AGS1 16x10GE
1 16 AGS2 ABR B1
A1
AGS1 AGS1 16x10GE

1 16 AGS2 Not
DSLAM B1 LSR
1 - 200 supported
. B
ABR A2
.
.
AGS1 AGS1 10x10GE ABR B2
1 16 AGS2
A1 L1 area2
AGS1 AGS1 10x10GE
DSLAM 1 16 AGS2
1 - 200 B1
ISIS Design - Areas
static 3. Redistribute Backbone Loopbacks 2. NO redistribution 1. Redistribute

into level1 Into level 2 static
into level1
ISIS L2
ISIS L1 ISIS L1
STATIC STATIC
L1 L2 L2 L1
Label DoD Label DoD
L1 L1/L2 L2 L2 L1/L2 L1
DSLAM 1
DSLAM 2
1. Access is static
• Redistribute static into level1 / label downstream on demand (DoD)
2. Aggregation is ISIS level 1 only with LDP

• Do NOT redistribute L1 into L2
3. Backbone is ISIS level 2 only with LDP

• Redistribute Backbone Loopbacks into L1
ISIS Design - Areas
static Redistribute Backbone Loopbacks NO redistribution Redistribute

into level1 Into level 2 static
into level1
ISIS L2
ISIS L1 ISIS L1
STATIC STATIC
L1 L2 L2 L1
Label DoD Label DoD
L1 L1/L2 L2 L2 L1/L2 L1
DSLAM 1
DSLAM 2
Reachability Reachability Reachability

within area within backbone within area
and backbone
Up to 1000 nodes
100s of nodes
100s of nodes
iBGP Design
Use BGP for inter-Area IP and MPLS reachability
static Route Reflection Route Reflection Redistribute static

Into iBGP
Redistribute Loopback
Into iBGP
iBGP IPv4+label iBGP IPv4+label iBGP IPv4+label
ISIS L2
ISIS L1 ISIS L1
STATIC L1 L2 L2 L1 STATIC
L1 L1/L2 L2 L2 L1/L2 L1
DSLAM 1
DSLAM 2
1. Redistribute all loopbacks from access and aggregation into iBGP.

2. Advertize the Loopbacks to all edge nodes outsite the area
3. UseABR to reflect iBGP routes between area-backbone-area
• ABR is acting as a inter-area Route Reflector
• ABR A2 and B2 is setting „Next Hop Self“
Control Plane - iBGP
iBGP: NO next hop self / add-path iBGP: next hop self / add-path BGP/ISIS: redistribute static
BGP: X -> B1/b1 BGP: X -> A1 / a1 BGP: X -> R1 / r1 BGP: X -> R1 / -
-> B2/b2 -> A2 / a2 -> R2 / r2 -> R2/r2
ISIS: A1 -> AGS2A1
-> AGS2B1 ISIS: A1 -> LSRA1 ISIS: X -> AGS2A2 ISIS: X -> static
A2 -> AGS2A1 -> LSRB1 -> AGS2B2 -> AGS2A2
-> AGS2B1 A2 -> LSRA1 -> ABRB2 -> AGS2B2
-> LSRB1 R1, R2 -> AGS2A2 R2 -> AGS2A2
RIB: X -> A1 -> AGS2B2 -> AGS2B2
-> A2 RIB: X -> A1 -> ABRB2
-> A2 RIB: X -> interface
A1 -> AGS2A1 A1 -> LSRA1 RIB: X -> AGS2A2 R1 -> connected
-> AGS2B1 -> LSRB1 -> AGS2B2 R2 -> AGS2A2
A2 -> AGS2A1 A2 -> LSRA1 R1, R2 -> AGS2A2 -> AGS2B2
-> AGS2B1 -> LSRB1 -> AGS2B2
iBGP IPv4+label iBGP IPv4+label

iBGP IPv4+label
ISIS L2
ISIS L1 ISIS L1
L0=B1 L0=A1
L1 L2 L2 L1

L0=X
L0=R1
L1 L1/L2 L2 L2 L1/L2 L1
L0=R2
DSLAM 1
DSLAM 2

L0=B2
L0=A2
Control Plane Scale:

– 100.000 routes in BGP and RIB table on each BGP speaker
Pseudo wire label
BGP label
Forwarding Plane LDP label
iBGP: NO next hop self / add-path iBGP: next hop self / add-path BGP/ISIS: redistribute static
BGP: X -> B1/b1 BGP: X -> A1 / a1 BGP: X -> R1 / r1 BGP: X -> R1 / -
-> B2/b2 -> A2 / a2 -> R2 / r2 -> R2/r2
ISIS: A1 -> AGS2A1
-> AGS2B1 ISIS: A1 -> LSRA1 ISIS: X -> AGS2A2 ISIS: X -> static
A2 -> AGS2A1 -> LSRB1 -> AGS2B2 -> AGS2A2
-> AGS2B1 A2 -> LSRA1 -> ABRB2 -> AGS2B2
-> LSRB1 R1, R2 -> AGS2A2 R2 -> AGS2A2
RIB: X -> A1 -> AGS2B2 -> AGS2B2
-> A2 RIB: X -> A1 -> ABRB2
-> A2 RIB: X -> interface
A1 -> AGS2A1 A1 -> LSRA1 RIB: X -> AGS2A2 R1 -> connected
-> AGS2B1 -> LSRB1 -> AGS2B2 R2 -> AGS2A2
A2 -> AGS2A1 A2 -> LSRA1 R1, R2 -> AGS2A2 -> AGS2B2
-> AGS2B1 -> LSRB1 -> AGS2B2
iBGP IPv4+label iBGP IPv4+label

iBGP IPv4+label
ISIS L2
ISIS L1 L0=B1 L0=A1 ISIS L1
L1 L2 L2 L1

L0=X
L0=R1
L1 L1/L2 L2 L2 L1/L2 L1
L0=R2
DSLAM 1
DSLAM 2
AGS1 B1 AGS2 B1 ABR B1 LSR B1 LSR B2 ABR B2 AGS2 B2 AGS1 B2

L1 L2 L2 L1
L0=B2
L0=A2
push
push push Pop/push swap pop
swap swap swap swap pop
Forwarding
Lab Overview
Lab Topology
RR1
192.168.100.100
CE1 PE1 D1 ASBR2 P1 P3 ASBR3 D3 PE3 CE3

172.16.1.1 192.168.1.1 192.168.3.3 192.168.5.5 192.168.7.7 192,168.9.9 192.168.11.11 192.168.13.13 192.168.15.15 172.16.3.3
PE2 D2 ASBR1 P2 ASBR4 PE2 PE4

CE2 P4 CE4
192.168.2.2 192.168.4.4 192.168.6.6 192.168.8.8 192.168.12.12 192.168.14.14 192.168.16.16
192.168.10.10
SP Core Network IP Addressing

Loopback - 192.168.x.x/32
Interface - 10.x.y.x/24 RR2
192.168.200.200
Customer Prefixes
Lab Topology
RR1
192.168.100.100
Gi0/1 Gi0/2
CE1 PE1 D1 ASBR2 P1 Gi0/0/0/0 P3 ASBR3 D3 PE3 CE3

172.16.1.1 192.168.1.1 192.168.5.5 192.168.7.7 Gi2 192.168.11.11 192.168.13.13 172.16.3.3
192.168.3.3 192,168.9.9 192.168.15.15
Gi2 Gi4 Gi0/3 Gi0/0/0/2 Gi0/0/0/3 Gi5 Gi3 Gi0/3 Gi4 Gi2
Gi0/1 Gi0/1 Gi0/0/0/0 Gi0/0/0/1 Gi Gi0/0/0/2 Gi0/0/0/0 Gi0/1 Gi0/1
0/ 6
0/ 0 Gi
/4
Gi3 Gi0/2 Gi0/0/0/1 Gi0/0/0/2 Gi0/0/0/1 Gi0/2 Gi3

Gi6
Gi4
Gi2 Gi0/1 Gi0/0/0/0 Gi5 Gi0/0/0/3 Gi0/0/0/1 Gi0/3 Gi0/1 Gi2
Gi0/1 Gi4 Gi0/3 Gi0/0/0/2 Gi3 Gi0/0/0/2 Gi0/0/0/0 Gi4 Gi0/1
PE2 D2 ASBR1 P2 Gi2 Gi0/0/0/0 ASBR4 PE2 PE4

CE2 P4 CE4
192.168.2.2 192.168.4.4 192.168.6.6 192.168.8.8 192.168.12.12 192.168.14.14 192.168.16.16
192.168.10.10
Gi0/1 Gi0/2
SP Core Network IP Addressing

Interface - 10.x.y.x/24 RR2
192.168.200.200
Customer Prefixes
Central RR
RR1
192.168.100.100
Inline RR Inline RR
172.16.1.1 192.168.1.1 192.168.3.3 192.168.5.5 192.168.7.7 192,168.9.9 192.168.11.11 192.168.13.13 192.168.15.15 172.16.3.3

CE2 P4 CE4
192.168.2.2 192.168.4.4 192.168.6.6 192.168.8.8 192.168.12.12 192.168.14.14 192.168.16.16
192.168.10.10
Inline RR Inline RR
IS-IS Level-1 IS-IS Level-1
RR2
192.168.200.200
IS-IS Level-2 Central RR
BGP AS 6500
Central RR
RR1
iBGP + Label 192.168.100.100 iBGP + Label
iBGP + Label iBGP + Label
(BGP LU) (BGP LU)
(BGP LU) (BGP LU)
Route Reflection Route Reflection
Inline RR Inline RR
172.16.1.1 192.168.1.1 192.168.3.3 192.168.5.5 192.168.7.7 192,168.9.9 192.168.11.11 192.168.13.13 192.168.15.15 172.16.3.3

CE2 P4 CE4
192.168.2.2 192.168.4.4 192.168.6.6 192.168.8.8 192.168.12.12 192.168.14.14 192.168.16.16
192.168.10.10
Inline RR Inline RR

(BGP LU) (BGP LU)
Route Reflection RR2 Route Reflection
(BGP LU) (BGP LU)
192.168.200.200
BGP AS 6500
Central RR PW label / VPN Label
RR1 BGP label
192.168.100.100 LDP label
Inline RR Inline RR
172.16.1.1 192.168.1.1 192.168.3.3 192.168.5.5 192.168.7.7 192,168.9.9 192.168.11.11 192.168.13.13 192.168.15.15 172.16.3.3

CE2 P4 CE4
192.168.2.2 192.168.4.4 192.168.6.6 192.168.8.8 192.168.12.12 192.168.14.14 192.168.16.16
192.168.10.10
Inline RR Inline RR
RR2
192.168.200.200
BGP AS 6500
push pop
push push Pop/push swap
swap swap swap pop
Forwarding
Lets LAB IT!
Troubleshooting
1. Verifying the Configuration
- Global Configuration
- Interface level Configuration
- Routing Protocol Configuration
2. Monitoring the state of the tunnel

- Information Distribution
- Path Calculation
- Path Setup
- Forwarding traffic down a tunnel
3. Finding the Root cause of the Problem
4. Common Problem Scenarios (Test cases)

- Is the Path Valid
- Forwarding down or taking the tunnel
5. Summary
Cisco Spark
Questions?
Use Cisco Spark to communicate
with the speaker after the session
How
1. Find this session in the Cisco Live Mobile App
2. Click “Join the Discussion”
3. Install Spark or go directly to the space
4. Enter messages/questions in the space
cs.co/ciscolivebot#LTRMPL-3843
• Please complete your Online Complete Your Online
Session Evaluations after each
session
Session Evaluation
• Complete 4 Session Evaluations
& the Overall Conference
Evaluation (available from
Thursday) to receive your Cisco
Live T-shirt
• All surveys can be completed via
the Cisco Live Mobile App or the
Communication Stations
Don’t forget: Cisco Live sessions will be available
for viewing on-demand after the event at
www.ciscolive.com/global/on-demand-library/.
Continue Your Education
• Demos in the Cisco campus
• Walk-in Self-Paced Labs
• Tech Circle
• Meet the Engineer 1:1 meetings
• Related sessions
Thank you

LTRMPL 3843

Uploaded by

Copyright:

Available Formats

You might also like

LTRMPL 3843

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

LTRMPL 3843

Uploaded by

Copyright:

Available Formats

LTRMPL-3843

Design, Deployment and

Vinit Jain, Technical Leader Services CCIE # 22854

Deployment Network Size Access Type Core/Aggregation LSP

LDP LSP LDP LSP LDP LSP

• Core and Aggregation Networks enable Unified MPLS Transport

• Core, Aggregation, Access Network enable Unified MPLS Transport

AGS1 A1 AGS2 A1 ABR A1 LSR A1 LSR A2 ABR A2 AGS2 A2 AGS1 A2

AGS1 B1 AGS2 B1 L1 ABR B1 L2 LSR B1 LSR B2 L2 ABR B2 L1 AGS2 B2 AGS1 B2

1.000 Nodes / Core

10.000 Nodes / Aggregation

100.000 Nodes / Access

AGS1 AGS1B 16x10GE

AGS1 AGS1 16x10GE

static 3. Redistribute Backbone Loopbacks 2. NO redistribution 1. Redistribute

AGS1 B1 AGS2 B1 L1 ABR B1 L2 LSR B1 LSR B2 L2 ABR B2 L1 AGS2 B2 AGS1 B2

2. Aggregation is ISIS level 1 only with LDP

3. Backbone is ISIS level 2 only with LDP

static Redistribute Backbone Loopbacks NO redistribution Redistribute

AGS1 B1 AGS2 B1 L1 ABR B1 L2 LSR B1 LSR B2 L2 ABR B2 L1 AGS2 B2 AGS1 B2

Reachability Reachability Reachability

static Route Reflection Route Reflection Redistribute static

iBGP IPv4+label iBGP IPv4+label iBGP IPv4+label

AGS1 B1 AGS2 B1 L1 ABR B1 L2 LSR B1 LSR B2 L2 ABR B2 L1 AGS2 B2 AGS1 B2

1. Redistribute all loopbacks from access and aggregation into iBGP.

iBGP IPv4+label iBGP IPv4+label

AGS1 A1 AGS2 A1 ABR A1 LSR A1 LSR A2 ABR A2 AGS2 A2 AGS1 A2

AGS1 B1 AGS2 B1 L1 ABR B1 L2 LSR B1 LSR B2 L2 ABR B2 L1 AGS2 B2 AGS1 B2

Control Plane Scale:

iBGP IPv4+label iBGP IPv4+label

AGS1 A1 AGS2 A1 ABR A1 LSR A1 LSR A2 ABR A2 AGS2 A2 AGS1 A2

AGS1 B1 AGS2 B1 ABR B1 LSR B1 LSR B2 ABR B2 AGS2 B2 AGS1 B2

CE1 PE1 D1 ASBR2 P1 P3 ASBR3 D3 PE3 CE3

PE2 D2 ASBR1 P2 ASBR4 PE2 PE4

SP Core Network IP Addressing

CE1 PE1 D1 ASBR2 P1 Gi0/0/0/0 P3 ASBR3 D3 PE3 CE3

Gi3 Gi0/2 Gi0/0/0/1 Gi0/0/0/2 Gi0/0/0/1 Gi0/2 Gi3

PE2 D2 ASBR1 P2 Gi2 Gi0/0/0/0 ASBR4 PE2 PE4

SP Core Network IP Addressing

PE2 D2 ASBR1 P2 ASBR4 PE2 PE4

PE2 D2 ASBR1 P2 ASBR4 PE2 PE4

iBGP + Label iBGP + Label

PE2 D2 ASBR1 P2 ASBR4 PE2 PE4

2. Monitoring the state of the tunnel

3. Finding the Root cause of the Problem

4. Common Problem Scenarios (Test cases)

You might also like