Design, Deployment and Troubleshooting Scalable MPLS ... · • The network domains are interconnected with hierarchical LSPs based on RFC 3107, BGP IPv4+labels

Design, Deployment and Troubleshooting Scalable MPLS Architecture (Platform : IOS-XR, IOS-XE)

Vinit Jain, Technical Leader Services CCIE # 22854Twitter @vinugenie

Shashi Shekhar Sharma, Customer Advocacy EngineerTwitter @Shekhar1988

LTRMPL-3843

© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public

Cisco Spark

Questions? Use Cisco Spark to communicate with the speaker after the session

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

How

cs.co/ciscolivebot#LTRMPL-3843

• Introduction

• Seamless MPLS Overview

• Deployment Models

• Design Breakdown

• Lab Overview and Packet Flow

• Control and Forwarding Plane flow

• Accessing the Lab

• Lab it

Agenda


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

5LTRMPL-3843


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

6LTRMPL-3843


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.

7LTRMPL-3843

Why Scalable MPLS ?

© 2018 Cisco and/or its affiliates. All rights reserved. Cisco Public 9LTRMPL-3843

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

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.

MPLS in Access/Edge for benefits like better Scalability, TE, QOS and resiliency


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

11LTRMPL-3843


IMPLEMENTATION: SEAMLESS MPLSNetwork 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.

13LTRMPL-3843


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

14LTRMPL-3843

• Introduction

• Seamless MPLS Overview

• Deployment Models

• Design Breakdown

• Lab Overview and Packet Flow

• Accessing the Lab

• Lab it

Agenda


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

16LTRMPL-3843


Unified MPLS Architecture Models

• 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

Model

Network Size Access Type Core/Aggregation LSP

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

17LTRMPL-3843


1 – Small Network: Ethernet/TDM AccessFlat LDP LSP across Core and Aggregation Networks

• 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

Distribution Node

Core and Aggregation

IP/MPLS Domain

Core Node

Aggregation Node

Core Node

Core Node

Core Node

IGP/LDP domain

Aggregation Node

Aggregation Node

Aggregation Node

Aggregation Node

Pre-AggregationNode

IP/Ethernet

Fiber and Microwave3G/LTE

TDM and Packet Microwave, 2G/3G/LTE

Mobile Transport GW

Mobile Transport GW

Business

CSG


2 – Small Network: MPLS AccessHierarchical BGP LSP Across Core + Aggregation and Access Networks

• 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.

Core and Aggregation

IP/MPLS domain

IGP Area

Aggregation Node

Aggregation Node

Aggregation Node

Aggregation Node

Pre-AggregationNode

RANIP/MPLS Domain

LDP LSP LDP LSP LDP LSP

iBGP Hierarchical LSP

RANIP/MPLS Domain

Pre-AggregationNode

Mobile Transport GW

Core Node

Core Node

Core Node

Core Node

Mobile Transport GW

CSG

CSG

CSG

CSG

CSG

CSG


Core Network

IP/MPLS Domain

IP/Ethernet

Fiber and Microwave3G/LTE

20LTRMPL-3843

3 – Large Network: Ethernet/TDM access Hierarchical BGP LSP Across Core Network and Aggregation Networks

• 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.

Pre-Aggregation Node

Aggregation Network

IP/MPLS

Domain

Aggregation Node

AggregationNode

Aggregation Network

IP/MPLS

Domain

Core Node

LDP LSP LDP LSP LDP LSP

iBGP (eBGP across ASes) Hierarchical LSP

TDM and Packet Microwave, 2G/3G/LTE

Aggregation Node

Aggregation Node

Aggregation Node

Core Node

Core Node

Core Node

Mobile Transport GW

Mobile Transport GW

CSG

CSG


4 – Large Network: MPLS Access Hierarchical BGP LSP Across Core, Aggregation and Access Networks

• 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

RANIP/MPLSdomain

Core Node

Core Node

Core Node

Core Node

LDP LSP LDP LSP LDP LSP LDP LSP LDP LSP

iBGP (eBGP across ASes) Hierarchical LSP

RANIP/MPLS domain

Core Network

IP/MPLS Domain

Pre-Aggregation Node

Aggregation Network

IP/MPLS

Domain

Aggregation Node

Pre-AggregationNode

Aggregation Network

IP/MPLS

Domain

Core Node

Aggregation Node

Aggregation Node

Aggregation Node

Core Node

Core Node

Core Node

Mobile Transport GW

Mobile Transport GW

CSG

CSG

CSGCSG

CSG

CSG


5 - Large Network, MPLS AccessHierarchical BGP LSP with IGP/LDP Redistribution in Access Network

• 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

RANMPLS/IP

IGP Area/Process

RANMPLS/IP

IGP Area/Process

MPC iBGP community

into RAN IGP

RAN IGP CSN Loopbacks

into iBGP

Core

Core

Core

Core

LDP LSP LDP LSP LDP LSP LDP LSP

LDP LSP

i/eBGP Hierarchical LSP

Core Node

Core Node

Core Node

Core Node

Core Network

IP/MPLS Domain

Aggregation Network

IP/MPLS

Domain

Aggregation Node

Pre-AggregationNode

Aggregation Network

IP/MPLS

Domain

Core Node

Aggregation Node

Aggregation Node

Aggregation Node

Core Node

Core Node

Core Node

Mobile Transport GW

Mobile Transport GW

Pre-AggregationNode

MPC iBGP community

into RAN IGP

RAN IGP CSN Loopbacks

into iBGP

CSG

CSG

CSGCSG

CSG

CSG


Unified MPLS Architecture ModelsSummary 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

23LTRMPL-3843

Deployment

Model

Network Size Access Type Core/Aggregation LSP

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 networkfailures (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 withLFA for all failures (sub 50ms)

• BGP next-hop-self on RR / BGP add-path

LTRMPL-3843 24

Lets Break It Down

© 2018 Cisco and/or its affiliates. All rights reserved. Cisco PublicLTRMPL-3843

Reference Topology

ABR A1

ABR B1

AGS2 A1 LSR A1

LSR B1AGS2 B1

AGS1 A1

AGS1 B1

LSR A2

LSR B2 ABR B2 AGS1 B2

AGS1 A2AGS2 A2

AGS2 B2

ISIS L2ISIS L1

1.000 Nodes / Core

10.000 Nodes / Aggregation

100.000 Nodes / Access

L1

L1

L1

L2

L2

L2

ISIS L1

L1

L1

L1L2

L2

L2

DSLAM 2

L1/L2 L1/L2

DSLAM 1

ABR A2


AGS2 A1

AGS1A16

AGS11

16x10GE

AGS1B16

AGS11

16x10GE

AGS116

AGS11

16x10GE

AGS116

AGS11

16x10GE

AGS116

AGS11

16x10GE

AGS116

AGS11

16x10GE

AGS116

AGS11

10x10GE

AGS116

AGS11

10x10GE

AGS2 B1

AGS2 A1

AGS2 B1

AGS2 A1

AGS2 B1

AGS2 A1

AGS2 B1

LSR A

LSR B

ABR A1

ABR B1

L1 area1

.

.

.

DSLAM1 - 200

DSLAM1 - 200

DSLAM1 - 200

DSLAM1 - 200

ABR A2

ABR B2

L1 area2

Not supported

BRAS


ISIS Design - Areas

ABR A1

ABR B1

AGS2 A1 LSR A1

LSR B1AGS2 B1

AGS1 A1

AGS1 B1

LSR A2


AGS1 A2AGS2 A2

AGS2 B2

ISIS L2ISIS L1

L1

L1

L1

L2

L2

L2

ISIS L1

L1

L1

L1L2

L2

L2

DSLAM 2

L1/L2 L1/L2

DSLAM 1

ABR A2

STATIC

Label DoD

STATIC

Label DoD

1. Redistribute

static

into level1

2. NO redistribution

Into level 2

3. Redistribute Backbone Loopbacks

into level1

static

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

ABR A1

ABR B1

AGS2 A1 LSR A1

LSR B1AGS2 B1

AGS1 A1

AGS1 B1

LSR A2


AGS1 A2AGS2 A2

AGS2 B2

ISIS L2ISIS L1

L1

L1

L1

L2

L2

L2

ISIS L1

L1

L1

L1L2

L2

L2

DSLAM 2

L1/L2 L1/L2

DSLAM 1

ABR A2

Redistribute

static

into level1

NO redistribution

Into level 2

Redistribute Backbone Loopbacks

into level1

static

Reachability within backbone

Up to 1000 nodes

Reachability within area

100s of nodes

STATIC

Label DoD

STATIC

Label DoD

Reachability within areaand backbone

100s of nodes


iBGP DesignUse BGP for inter-Area IP and MPLS reachability

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“

ABR A1

ABR B1

AGS2 A1 LSR A1

LSR B1AGS2 B1

AGS1 A1

AGS1 B1

LSR A2


AGS1 A2AGS2 A2

AGS2 B2

ISIS L2ISIS L1

L1

L1

L1

L2

L2

L2

ISIS L1

L1

L1

L1L2

L2

L2

DSLAM 2

L1/L2 L1/L2

DSLAM 1

ABR A2

STATICSTATIC

Redistribute static

Into iBGP

Redistribute Loopback

Into iBGP

Route Reflectionstatic Route Reflection

iBGP IPv4+label iBGP IPv4+labeliBGP IPv4+label

LTRMPL-3843 30


ABR A1

ABR B1

AGS2 A1 LSR A1

LSR B1AGS2 B1

AGS1 A1

AGS1 B1

LSR A2

LSR B2

ABR A2

ABR B2 AGS1 B2

AGS1 A2AGS2 A2

AGS2 B2

ISIS L2ISIS L1

L1

L1

L1

L2

L2

L2

ISIS L1

L1

L1

L1L2

L2

L2

DSLAM 1DSLAM 2

L1/L2 L1/L2

Control Plane - iBGP


iBGP: next hop self / add-path

BGP: X -> R1 / r1-> R2 / r2

ISIS: X -> AGS2A2-> AGS2B2-> ABRB2

R1, R2 -> AGS2A2-> AGS2B2-> ABRB2

RIB: X -> AGS2A2-> AGS2B2

R1, R2 -> AGS2A2-> AGS2B2

BGP/ISIS: redistribute static

BGP: X -> R1 / --> R2/r2

ISIS: X -> static-> AGS2A2-> AGS2B2

R2 -> AGS2A2-> AGS2B2

RIB: X -> interfaceR1 -> connectedR2 -> AGS2A2

-> AGS2B2

BGP: X -> B1/b1 -> B2/b2

ISIS: A1 -> AGS2A1-> AGS2B1

A2 -> AGS2A1-> AGS2B1

RIB: X -> A1-> A2



iBGP: NO next hop self / add-path

BGP: X -> A1 / a1-> A2 / a2

ISIS: A1 -> LSRA1-> LSRB1

A2 -> LSRA1-> LSRB1

RIB: X -> A1-> A2

A1 -> LSRA1-> LSRB1

A2 -> LSRA1-> LSRB1

L0=XL0=R1

L0=A1L0=B1

Control Plane Scale:

– 100.000 routes in BGP and RIB table on each BGP speaker

L0=R2

L0=A2L0=B2

LTRMPL-3843 31


Forwarding Plane

Forwarding

push

swapPop/push

push

push

Pseudo wire label

BGP label

LDP label

swap

ABR A1

ABR B1

AGS2 A1 LSR A1

LSR B1AGS2 B1

AGS1 A1

AGS1 B1

LSR A2

LSR B2

ABR A2

ABR B2 AGS1 B2

AGS1 A2AGS2 A2

AGS2 B2

ISIS L2ISIS L1

L1

L1

L1

L2

L2

L2

ISIS L1

L1

L1

L1L2

L2

L2

DSLAM 1DSLAM 2

L1/L2 L1/L2


L0=XL0=R1

L0=A1L0=B1

L0=R2

L0=A2L0=B2

swap

iBGP: next hop self / add-path

BGP: X -> R1 / r1-> R2 / r2

ISIS: X -> AGS2A2-> AGS2B2-> ABRB2

R1, R2 -> AGS2A2-> AGS2B2-> ABRB2

RIB: X -> AGS2A2-> AGS2B2

R1, R2 -> AGS2A2-> AGS2B2

BGP/ISIS: redistribute static

BGP: X -> R1 / --> R2/r2

ISIS: X -> static-> AGS2A2-> AGS2B2

R2 -> AGS2A2-> AGS2B2

RIB: X -> interfaceR1 -> connectedR2 -> AGS2A2

-> AGS2B2

BGP: X -> B1/b1 -> B2/b2

ISIS: A1 -> AGS2A1-> AGS2B1


RIB: X -> A1-> A2



iBGP: NO next hop self / add-path

BGP: X -> A1 / a1-> A2 / a2

ISIS: A1 -> LSRA1-> LSRB1

A2 -> LSRA1-> LSRB1

RIB: X -> A1-> A2

A1 -> LSRA1-> LSRB1

A2 -> LSRA1-> LSRB1

swap popswappop

LTRMPL-3843 32

Lab Overview


Lab Topology

PE1192.168.1.1

PE2192.168.2.2

CE2

PE3192.168.15.15

PE4192.168.16.16

D1192.168.3.3

D2192.168.4.4

ASBR2192.168.5.5

ASBR1192.168.6.6

P1192.168.7.7

P2192.168.8.8

P3192,168.9.9

P4192.168.10.10

RR1192.168.100.100

RR2192.168.200.200

ASBR3192.168.11.11

ASBR4192.168.12.12

D3192.168.13.13

PE2192.168.14.14

SP Core Network IP AddressingLoopback - 192.168.x.x/32

Interface - 10.x.y.x/24

CE1172.16.1.1

CE3172.16.3.3

Customer PrefixesLoopback - 172.16.x.x/32

CE4

LTRMPL-3843 34


Lab Topology

PE1192.168.1.1

PE2192.168.2.2

CE2

PE3192.168.15.15

PE4192.168.16.16

D1192.168.3.3

D2192.168.4.4

ASBR2192.168.5.5

ASBR1192.168.6.6

P1192.168.7.7

P2192.168.8.8

P3192,168.9.9

P4192.168.10.10

RR1192.168.100.100

RR2192.168.200.200

ASBR3192.168.11.11

ASBR4192.168.12.12

D3192.168.13.13

PE2192.168.14.14

SP Core Network IP AddressingLoopback - 192.168.x.x/32

Interface - 10.x.y.x/24

CE1172.16.1.1

CE3172.16.3.3

Customer PrefixesLoopback - 172.16.x.x/32

CE4

Gi4

Gi0/1

Gi0/1

Gi4

Gi3 Gi0/2

Gi0/3

Gi0/3

Gi0/0/0/0

Gi0/0/0/0

Gi0/0/0/1

Gi0/0/0/2

Gi0/0/0/2

Gi0/0/0/1

Gi3

Gi4

Gi5

Gi2 Gi0/0/0/0

Gi0/0/0/3

Gi0/0/0/3

Gi0/0/0/2

Gi0/0/0/4

Gi6

Gi6

Gi5

Gi0/1 Gi0/2

Gi0/1 Gi0/2

Gi0/0/0/0 Gi2

Gi3

Gi0/0/0/2

Gi0/0/0/1

Gi0/0/0/2

Gi0/0/0/1

Gi0/3

Gi0/0/0/0

Gi0/3

Gi0/0/0/0

Gi0/2

Gi0/1

Gi0/1

Gi4

Gi4

Gi3

Gi2

Gi2

Gi2

Gi2

Gi0/1

Gi0/1

Gi0/1

Gi0/1

LTRMPL-3843 35


PE1192.168.1.1

PE2192.168.2.2

CE2

PE3192.168.15.15

PE4192.168.16.16

D1192.168.3.3

D2192.168.4.4

ASBR2192.168.5.5

ASBR1192.168.6.6

P1192.168.7.7

P2192.168.8.8

P3192,168.9.9

P4192.168.10.10

RR1192.168.100.100

RR2192.168.200.200

ASBR3192.168.11.11

ASBR4192.168.12.12

D3192.168.13.13

PE2192.168.14.14

CE1172.16.1.1

CE3172.16.3.3

CE4

IS-IS Level-1 IS-IS Level-1

IS-IS Level-2

BGP AS 6500Central RR

Central RR

Inline RR

Inline RR

Inline RR

Inline RR

LTRMPL-3843 36


PE1192.168.1.1

PE2192.168.2.2

CE2

PE3192.168.15.15

PE4192.168.16.16

D1192.168.3.3

D2192.168.4.4

ASBR2192.168.5.5

ASBR1192.168.6.6

P1192.168.7.7

P2192.168.8.8

P3192,168.9.9

P4192.168.10.10

RR1192.168.100.100

RR2192.168.200.200

ASBR3192.168.11.11

ASBR4192.168.12.12

D3192.168.13.13

PE2192.168.14.14

CE1172.16.1.1

CE3172.16.3.3

CE4


IS-IS Level-2


Central RR

Inline RR

Inline RR

Inline RR

Inline RR

iBGP + Label

(BGP LU)

iBGP + Label

(BGP LU)

iBGP + Label

(BGP LU)

Route Reflection

iBGP + Label

(BGP LU)

Route Reflection

iBGP + Label

(BGP LU)

Route Reflection

iBGP + Label

(BGP LU)

Route Reflection

iBGP + Label

(BGP LU)

iBGP + Label

(BGP LU)

LTRMPL-3843 37


PE1192.168.1.1

PE2192.168.2.2

CE2

PE3192.168.15.15

PE4192.168.16.16

D1192.168.3.3

D2192.168.4.4

ASBR2192.168.5.5

ASBR1192.168.6.6

P1192.168.7.7

P2192.168.8.8

P3192,168.9.9

P4192.168.10.10

RR1192.168.100.100

RR2192.168.200.200

ASBR3192.168.11.11

ASBR4192.168.12.12

D3192.168.13.13

PE2192.168.14.14

CE1172.16.1.1

CE3172.16.3.3

CE4


IS-IS Level-2


Central RR

Inline RR

Inline RR

Inline RR

Inline RR

Forwarding

push

swapPop/push

push

push

swapswap

swap pop

pop

PW label / VPN Label

BGP label

LDP label

LTRMPL-3843 38


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

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

How

cs.co/ciscolivebot#LTRMPL-3843


• Please complete your Online Session Evaluations after each session

• 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/.

Complete Your Online Session Evaluation

http://ciscolive.com/Online

http://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

43LTRMPL-3843

Thank you

Design, Deployment and Troubleshooting Scalable MPLS ... · • The network domains are interconnected with hierarchical LSPs based on RFC 3107, BGP IPv4+labels

Documents